-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Missing execution steps statuses if same step is called multiple times in a test #23
Comments
Cheers! On reflection this probably shouldn't be a Unfortunately I have very little time available at present. |
Hi! Thanks for the answer and insight, I tried it on my local environment, it seems to work fine. |
You'll have to fork and submit a pull request from that fork. |
Ok thank you very much for the quick reply! I added a PR with code Do you have any idea about the timeline of this PR validation / merging and the cucumber release process ? |
Cheers.
Typically it's good to add tests. In this case, we pull the tests from the CCK, so it would be better to add an example of it there. I'll make an issue for that. We can skip it for this PR.
We've setup our CI to make releases whenever. So probably as soon as the PR is megeged it can be released. Inclusion in Cucumber JVM may take a bit longer (depending on how quickly cucumber/cucumber-jvm#2826 can be resolved). The biggest bottleneck and most difficult factor to predict is my own availability. Unfortunately I can't make releases from my phone just yet. 😄 |
Hello!
I am not sure I created the bug in the right project, please excuse me if I got it wrong, and please let me know where this issue should be created.
👓 What I see :
I have a cucumber test where I call the same step multiple times :
When I launch the test, using
mvn test
with this option :-Dcucumber.plugin="html:target/html-report.html,junit:target/report.xml"
I noticed than the output in the xml report is incorrect.
The step "I add to cart" which is called two times in the test, is only displayed once (in this case, all steps are PASSED, and the last call is missing).
The HTML report is accurate and does not have this bug.
✅ What did you expect to see?
I expect to see a perfect match between the steps and the output in the xml report :
📦 Which tool/library version are you using?
I am using cucumber 7.14.0
Bug was seen when launching on both linux and windows environments.
Here is the pom :
🔬 How could we reproduce it?
Simply create a test and call the same step several times, and launch the test using
Dcucumber.plugin="html:target/html-report.html,junit:target/report.xml"
📚 Any additional context?
This text was originally generated from a template, then edited by hand. You can modify the template here.
The text was updated successfully, but these errors were encountered: