You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the DataProvider method is being called again, and I can see a newly generated UUID in the ParameterHandler.ParameterBag within the org.testng.internal.invokers.TestInvoker.retryFailed() method, it seems that the new value is not being propagated to the test method. Instead, the TestMethodArguments continues to hold the original value.
TestNG Version
Expected behavior
Regenerated (new) parameter value is passed to the test method on retry when DataProvider method contains attribute 'cacheDataForTestRetries = false'
Actual behavior
Original (initial) parameter value is passed to the test method on retry when DataProvider method contains attribute 'cacheDataForTestRetries = false'
Is the issue reproducible on runner?
Test case sample
The output during the test run is as follows:
While the DataProvider method is being called again, and I can see a newly generated UUID in the ParameterHandler.ParameterBag within the org.testng.internal.invokers.TestInvoker.retryFailed() method, it seems that the new value is not being propagated to the test method. Instead, the TestMethodArguments continues to hold the original value.
Relates to: #3076
Contribution guidelines
Incase you plan to raise a pull request to fix this issue, please make sure you refer our Contributing section for detailed set of steps.
The text was updated successfully, but these errors were encountered: