-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Null Pointer occurs when a Retried test has an exception in DataProvider #2157
Milestone
Comments
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Oct 1, 2019
2 tasks
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Oct 1, 2019
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Oct 2, 2019
krmahadevan
added a commit
that referenced
this issue
Oct 2, 2019
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Mar 17, 2023
Closes testng-team#2884 When a data driven test fails, then ensure that we don’t call the data provider once again when retrying the test (we seem to invoke the data provider multiple times, but ignore the value) As part of fixing this, getting rid of the test for testng-team#2157. testng-team#2157 - deals with null pointer exceptions arising Out of data provider that was re-invoked as a result Of us retrying a failed test. But now since a data provider is NOT going to be re-invoked the changes for testng-team#2157 become irrelevant.
3 tasks
krmahadevan
added a commit
that referenced
this issue
Mar 20, 2023
Closes #2884 When a data driven test fails, then ensure that we don’t call the data provider once again when retrying the test (we seem to invoke the data provider multiple times, but ignore the value) As part of fixing this, getting rid of the test for #2157. #2157 - deals with null pointer exceptions arising Out of data provider that was re-invoked as a result Of us retrying a failed test. But now since a data provider is NOT going to be re-invoked the changes for #2157 become irrelevant.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TestNG Version
7.0.0
Also reproducible on:
6.14.3, 7.0.0beta1
Expected behavior
The test should be in Skipped status.
A checked exception occurred in DataProvider should be handled.
Actual behavior
Is the issue reproductible on runner?
Test case sample
The test case is implemented in the project below.
https://github.com/OstapJ/testng-issue-retry-dataprovider
The test with Retry and DataProvider
DataProvider with exception
The text was updated successfully, but these errors were encountered: