jenkinsci / jenkinsci/nunit-plugin
Failure on teardown is not considered as test error/failure
- Dominant language
- Java
- Stars
- 44
- Forks
- 57
- Avg merge
- 4h 34m
- Merged PRs (30d)
- 1
Description
### Jenkins and plugins versions report
Jenkins: 2.346.3
OS: Windows Server 2019 - 10.0
Java: 1.8.0_402 - Amazon.com Inc. (OpenJDK 64-Bit Server VM)
---
nunit:0.27
xunit:3.1.0
### What Operating System are you using (both controller, and any agents involved in the problem)?
Windows Server 2019 - 10.0
### Reproduction steps
* On one of test-suite, error on teardown occurred (test executed successfully and passed):
executed="True" result="Failure" success="False"
* On general status of test-results:
errors="0" failures="0"
### Expected Results
* On one of test-suite, error on teardown occurred (test executed successfully and passed):
executed="True" result="Failure" success="False"
* On general status of test-results:
errors="1" failures="1"
### Actual Results
* On one of test-suite, error on teardown occurred (test executed successfully and passed):
executed="True" result="Failure" success="False"
* On general status of test-results:
errors="0" failures="0"
### Anything else?
Would be nice to have an option on the plugin to treat errors on any part of the test as a failure
### Are you interested in contributing a fix?
_No response_
Contributor guide
Research direction
Start by reproducing the teardown-error scenario with the reported Jenkins, NUnit, and xUnit versions on Windows. Trace how the plugin aggregates suite results when a test has result="Failure" and success="False"; done means the overall result reports errors="1" and failures="1", with the requested behavior covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100