-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IDEA test results tree #181
Comments
Although #211 was reported after this ticket it contains more info to fix this bug, so I'm closing this as a dupe. Thanks for the detailed report! |
Maybe I'm mistaken, but isn't the problem here that the background steps appear outside the Feature/Scenario/Step hierarchy? I have the same phenomenon in Eclipse, but I'm not sure what the expected behaviour is here. I would like background steps to appear within each scenario to which they apply, before any of the scenario-specific steps. If this is indeed the expected behaviour then this issue constitues a bug (independent from #211) because even though steps in a CucumberBackground are not reported to JUnit via the Runner.getChildren() method, they are reported on via the JUnitReporter, creating "unrooted test" reports in Eclipse and presumably the report as shown above in IDEA. If background steps are not supposed to appear in the report at all (as was the case in previous versions of cucumber-jvm), then the bug is that they get reported on via the JUnitReporter. In that case I'd also ask why they should not appear, since hiding them confuses the user because they are executed after all. I hope I made myself clear. So what is the expected behaviour here? |
the original bug is reproduced in cucumber-jvm 1.1.5 |
I face the same issue in cucumber-jvm 1.1.5 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
If running tests with cucumber-junit via idea, background steps results have invalid locations in tree
A.feature
B.feature
The text was updated successfully, but these errors were encountered: