-
Bug
-
Resolution: Fixed
-
Minor
-
Hudson 1.381
When all JUnit tests are skipped, the JUnit result archiver considers the build to have failed, since pass count and fail count are both zero.
I believe that the attached patch would fix the problem, though I haven't succeeded to build it and test it.
- is related to
-
JENKINS-22747 Add Job Configuration Option to NOT fail JUnit Report publish when no xml report files
-
- Resolved
-
Can't this just be made an option, a checkbox to optionally mark a build as not failed if all tests were skipped?
Here's an example use case where the project should not fail if there are no tests.
I have to run integration tests in project A against an unreliable customer's system; I use xslt in a separate project B to filter out only project A tests that failed due to that customer system, by marking all other tests as skipped. When there are no tests after filtering, project B contains no tests, indicating merely that the customer's system behaved for once. Currently Jenkins says such builds are failures; obviously in this use case the opposite is true.