Skip to content
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

TestNG: run each feature as separate TestNG test #817

Merged
merged 3 commits into from
Mar 18, 2015

Conversation

brasmusson
Copy link
Contributor

This PR is a copy of #653, rebased on the current tip of master (and with some comments fixed).

The idea is to let cucumber-testng run each Cucumber Feature as a separate TestNG test case (instead of wrap all the Cucumber Features into one TestNG test case). Then the notifications and/or reports generated natively by the TestNG runner will have results for each Cucumber Feature instead of only one result for the execution as a whole, see #653 for further details.

Closes #653.

ushkinaz and others added 3 commits January 1, 2015 21:05
* No wildcards
* TestNGCucumberRunnerTest rewritten to comply strict policy of code reviewers
* Stricter members access
Use custom reporter to detect feature failures instead of creating a new
runtime for each feature. Print summary and snippets at the end of the
run. Use feature files in src/test/resource/cucumber/runtime/testng
for the test of TestNGCucumberRunner.getFeatures().
Add new test runner class to examples/java-calculator-testng to show
how to run each feature as separate TestNG test by composition.
@aslakhellesoy
Copy link
Contributor

LGTM!

@brasmusson brasmusson merged commit 22d21be into cucumber:master Mar 18, 2015
brasmusson added a commit that referenced this pull request Mar 18, 2015
@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants