-
-
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
Generating step definitions with Cucumber 6 vs Cucumber 5 #2024
Labels
⚡ enhancement
Request for new functionality
Milestone
Comments
NicolasLauwereys
changed the title
Generating step definitions with Cucumber 6 in the way it used to be in Cucumber 5
Generating step definitions with Cucumber 6 vs Cucumber 5
Jun 15, 2020
mpkorstanje
added a commit
that referenced
this issue
Jan 17, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI + summary printer TODO what about: - CLI + summary printer + teamcity plugin? - JUnit4 with per-step reporting? - #2024
mpkorstanje
added a commit
that referenced
this issue
Jan 23, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI + summary printer TODO what about: - CLI + summary printer + teamcity plugin? - JUnit4 with per-step reporting? - #2024
mpkorstanje
added a commit
that referenced
this issue
Jan 23, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI + summary printer TODO what about: - CLI + summary printer + teamcity plugin? - JUnit4 with per-step reporting? - #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI + summary printer TODO what about: - CLI + summary printer + teamcity plugin? - JUnit4 with per-step reporting? - #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 - Teamcity Plugin When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI When printing snippets they should be copy-pasted into an IDE without further editing. This means individual snippets or groups of snippets should not be separated by spacers, text or anything else. Fixes: #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 - Teamcity Plugin When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI When printing snippets they should be copy-pasted into an IDE without further editing. This means individual snippets or groups of snippets should not be separated by spacers, text or anything else. Fixes: #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 - Teamcity Plugin When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI When printing snippets they should be copy-pasted into an IDE without further editing. This means individual snippets or groups of snippets should not be separated by spacers, text or anything else. Fixes: #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 - Teamcity Plugin When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI When printing snippets they should be copy-pasted into an IDE without further editing. This means individual snippets or groups of snippets should not be separated by spacers, text or anything else. Fixes: #2024
mpkorstanje
added a commit
that referenced
this issue
Feb 13, 2021
The various ways to execute Cucumber report undefined steps inconsistently. Partially because different tools have different reporting needs. Nevertheless: When reporting per scenario the suggestion should include snippets for all undefined steps in that scenario. This applies to: - JUnit4 - TestNG - JUnit5 - Teamcity Plugin When reporting per test run the suggestion should include snippets for all undefined steps in the execution. This applies to: - CLI When printing snippets they should be copy-pasted into an IDE without further editing. This means individual snippets or groups of snippets should not be separated by spacers, text or anything else. Fixes: #2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
When executing unimplemented scenarios with Cucumber 5 and JUnit you get an uninterrupted list of all unimplemented steps at the end of the output, so you can copy-paste those directly into your steps definitions class and start implementing.
When using Cucumber 6 however, it seems the generated steps are only displayed with other output inbetween. There is no uninterrupted list at the end of the ouput.
We would like this feature to also be added to Cucumber 6.
Example output with Cucumber 5
The text was updated successfully, but these errors were encountered: