Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not A Defect
-
None
Description
When I have a single cucumber test, the following is printed on my console:
Build step 'Publish Cucumber test result report' changed build result to FAILURE
According to the official terminology this should be marked as "unstable" instead, since "failure" indicates a unsuccessful build.
This consequently causes subsequent tasks in the pipeline to not trigger. The only workarround - triggering on failure - will result on broken builts getting deployed as well. Instead, I want to deploy with broken tests, but not with broken build (on development deployment).
Please note, that these options were also implemented in the other cucumber reports plugin in the "advanced" settings. Your plugin integrates much better inside Jenkins, so we really want to stay with you!
if your tests assertion is not correct then the build is correctly marked as unstable.
if your tests error (that is that they failed to run due to glue failure or are pending/undefined) then this is classed as an error in your tests (rather than being unstable - which is that the tests are fine but the result is not expected) and this is currently behaving correctly.
so unless you can supply a json file that shows contrary to this then this is not a defect - but possibly a dupe of JENKINS-30083