-
Notifications
You must be signed in to change notification settings - Fork 120
is there way to generate single rerun.txt file after the parallel test is completed #65
Comments
Hello @mmuntakim15, Thanks for appreciation. I had this changes but removed for purpose "tagwise parallel re-runner". Please try steps mentioned in comments #53. If you still face issue let us know, we will fix it. |
Hi @sugatmankar thanks for your reply. I understand that in version 2.0.0 we will have the parallel rerun functionality, My question was more toward is there rerun functionality exists in current version 1.2.1, which we are using currently, please let me know if you need further details. |
At the moment I don't think it will work in 1.2.1, since the rerun.txt file would probably be corrupted/overwritten when the Cucumber runners are running in parallel. I haven't tested it, but you could try using 2.0.0 will provide proper support for rerunning and should be ready before too long. |
2.0.1 is now released supporting parallel running of scenarios. |
Duplicate of issue #31 |
Hi All, I have set up a Selenium Java (Cucumber) framework for my project and I am stuck in the same issue. I want to generate a single rerun file having all the failed test cases/ scenarios in them after performing parallel execution (using Junit), how can the same be achieved ? I am using below versions: Can you please help me out on this? Thanks |
Hi, Is there way to generate single rerun.txt file after the parallel tests are completed so we can just rerun all failed tests as post single thread instead rerun it in parallel mode. For example. currently when we run parallel tests using this plugin, we don't have the capability to add "rerun:rerun.txt" plugin to all the runners. I know that this pull request is open related to rerun functionality. Please kindly let us know if this pull request will fix our issue. Btw thanks for building this plugin, It's been helping us everyday with our test execution.
Thanks
Mohammad
The text was updated successfully, but these errors were encountered: