Fix null pointer exception in TestNG when invalid options are used #1282
+8
−0
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.
Summary
Using invalid options through
cucumber.option
would cause thecreation of
testNGCucumberRunner
to fail with an exception. Howeverthis exception does not terminate TestNGs execution. This caused
additional exceptions in the data provider and tear down methods. The
additional exceptions were mistaken for the root cause, creating some
confusion.
Details
Output when using some invalid options
How Has This Been Tested?
Added a unit tests that exercises the data provider and tear down methods after a failed setup. Then removed this unit test because it modifies Env which influences all other tests.
Types of changes
Checklist: