-
Notifications
You must be signed in to change notification settings - Fork 120
Conversation
readme.md updated for Re-run functionality section.
Updated details about pom dependency
@temyers I need help to compare larger text. Could you please look IT/generic/generic runner build log? |
@temyers when im comparing expected with actual travis CI is failing but if i compare by removing \n and " in text file both are same . could you please have a look ?
|
I'll try and have a look. Probably a difference between windows/linux line endings/file encoding. |
I'm still not convinced that this is the right place for this functionality. Re-run implementation is already supported by the Surefire/Falsafe plugin and should be implemented there in my view. |
Also, please can you create an integration test to demonstrate (actually run the generated code) that this runner doesn't force the user to add additional dependencies. Ideally, using this plugin should not enforce the addition of any libraries. If it does, then those dependencies need to be explicit within the README. |
Added dependencies required.
@temyers i agree with you about re-run functionality added by Surefire/Failsafe but does they really have functionality to execute cucumbers in generic way ? Instead of depending on JUnit or TestNG why don't we directly interact with Cucumber CLI in generic way ? Why shouldn't we allow our plugin to have execution of only failed runner get trigger instantly ? Why should't our plugin generate consolidate reports run wise ? All this has been added to this PR. I have also updated README for explicit dependency. |
Also there is integration test in cucumber-jvm-parallel-plugin/src/it/generic-re-runner/ |
@sugatmankar This plugin generates the unit tests. The actual execution of tests is outside the scope of this plugin so I do not think it should be in here. However running tests and rerunning failing tests is a build-in feature of surefire and failsafe. https://maven.apache.org/surefire/maven-failsafe-plugin/examples/rerun-failing-tests.html @temyers might be best to just close this pull request. |
I'm closing this PR. A maven test runner that directly interacts with the cucumber command line is a good idea but also well out of scope for this plugin. It would probably be better of as a separate plugin. |
@mpkorstanje show me how you can rerun failed scenario with surefire or fail-safe. There is no solution as of now from sure fire. I would have close this so far before and for your info I have contributed too many changes that you weren't aware. By the way if you find solution let me know. |
The main objection is that rerunning tests and more in general the execution of tests is outside the scope of this plugin. That there is no solution is not a strong argument to add such a solution here. As it currently stands the rerun functionality is almost completely disjoint of the other functionality of this plugin. So if you have a strong and immediate need for this functionality I think the best option would be to create a separate maven plugin. I think you'll find it greatly reduces the complexity of the whole thing. I also have several lesser but nonetheless severe objections against the specific solution proposed here. By using the cucumber cli directly the rerun functionality does not play well with users who use glue code that depends on static and before class initializers in their customVmTemplate. I also find the addition of a report builder highly inappropriate. This plugin should be completely agnostic towards reporting. Never mind the requirement that end users add several dependencies to their build. |
That being said. I certainly wouldn't mind having some help in reviewing cucumber/cucumber-jvm#1035. It is the main blocker towards fixing surefire. |
Hi @temyers ,
I have re implemented rerunner, but only IT failing to compare Actual String and Expected string in verify.groovy in generic-re-runner IT. Do you have any suggestion to compare large text data.