-
-
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
[TestNG] Always map Pickles/TestCases to TestNG tests. #1339
Conversation
Remove the support for mapping the whole Cucumber test suite or each Cucumber feature to TestNG tests.
* | ||
* @see AbstractTestNGCucumberTests#runScenario(cucumber.api.testng.PickleEventWrapper, cucumber.api.testng.CucumberFeatureWrapper) | ||
*/ | ||
public class PickleEventWrapperImpl implements PickleEventWrapper { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably be package private.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to expose TestNGCucumberRunner
as part of the public api?
Nevermind. It appears we do. f27890e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CucumberFeatureWrapper.getCucumberFeature()
returns CucumberFeature
which falls outside of the public API I think it should be removed from the interface.
It also happens to go unused.
|
Everything else looks good to me. |
566da65
to
cb10e75
Compare
I'm moving the read me to a separate PR so I can also include #1338. |
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. |
Summary
Always map Pickles/TestCases to TestNG tests.
Details
Remove the support for mapping the whole Cucumber test suite or each Cucumber feature to TestNG tests.
Motivation and Context
The first TestNG support implemented in Cucumber-JVM mapped the whole Cucumber test suite to one TestNG test. It did enable running Cucumber from a TestNG runner, but did provide practically no notification of the result in the TestNG domain.
Later the TestNG support was expanded to allow the mapping of each Cucumber feature (file) to a TestNG test. It provided a little better notification of the result in the TestNG domain, but it was still limited.
Now the natural mapping, one Pickle/TestCase to one TestNG test, is supported, and a major release is on the way, the legacy support for mapping the whole Cucumber test suite or each Cucumber feature to TestNG tests should be removed.
How Has This Been Tested?
The automated test suite has been updated to cover the remaining behavior.
Types of changes
Checklist: