-
Bug
-
Resolution: Unresolved
-
Major
-
None
Background steps that passed are being displayed as undefined and the overall status of the feature is displayed as failed despite that all the scenario and background steps are passed. Attached is the screenshot.
[JENKINS-55369] Background step that passed is displayed as undefined
Lawrence Ajayi
created issue -
Damian Szczepanik
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Damian Szczepanik
made changes -
| Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |
Rebecca Warburton
added a comment - Hi, I am currently experiencing the same issue where a number of steps are reported as undefined in the report but they are defined in the steps file. They are defined in IntelliJ and everything has been committed to SVN which is being used to build the Jenkins job. I have also checked the step and feature files in the Workspace folder and there is a match between the 2 files so it shouldn't be undefined. I was hoping you could either reopen the issue or offer some guidenace on where this may be going wrong?
Rebecca Warburton
added a comment - Hi, I am currently experiencing the same issue where a number of steps are reported as undefined in the report but they are defined in the steps file. They are defined in IntelliJ and everything has been committed to SVN which is being used to build the Jenkins job. I have also checked the step and feature files in the Workspace folder and there is a match between the 2 files so it shouldn't be undefined. I was hoping you could either reopen the issue or offer some guidenace on where this may be going wrong? Rebecca Warburton
made changes -
| Resolution | Original: Fixed [ 1 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Lawrence Ajayi
added a comment - Hi, I also observed that the problem has not been fixed. Initially I thought the problem has been fixed and that, it will be applied in the next release but, this has not happened. At the moment all our tests are still showing the background steps as undefined and the features as failed despite the fact that all the scenario steps are shown as passed.
Lawrence Ajayi
added a comment - Hi, I also observed that the problem has not been fixed. Initially I thought the problem has been fixed and that, it will be applied in the next release but, this has not happened. At the moment all our tests are still showing the background steps as undefined and the features as failed despite the fact that all the scenario steps are shown as passed. 
Report this issue https://github.com/damianszczepanik/cucumber-reporting with the JSON file for the reference