Repository navigation
Run the Cucumber scenarios and show their counts - #7
Merged
Merged
Conversation
ashishb-automation
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The browser jobs previously finished green even though Maven reported zero tests. The JUnit Platform runner was being discovered, but it was not exposing the Cucumber scenarios to Surefire.
I switched the runner to Cucumber's TestNG integration and enabled the no-tests quality gate, so the build cannot pass silently with an empty suite again.
Each Chrome and Firefox job now shows total, passed, failed and skipped values in its Actions summary. The summary still appears on a failing run, and the detailed Cucumber and TestNG reports remain available as artifacts.
Checked in this pull request: