-
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
IHookable and IConfigurable callback discrepancy #2704
Comments
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Jan 12, 2022
Closes testng-team#2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
3 tasks
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Jan 15, 2022
Closes testng-team#2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Jan 18, 2022
Closes testng-team#2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Jan 18, 2022
Closes testng-team#2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
krmahadevan
added a commit
to krmahadevan/testng
that referenced
this issue
Jan 18, 2022
Closes testng-team#2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
krmahadevan
added a commit
that referenced
this issue
Jan 19, 2022
Closes #2704 Ensure that TestNG reports scenarios wherein User defines callbacks for configurations/test methods But fails to invoke those callbacks explicitly And also fails in shipping test status to a user recognized status (PASS|FAILURE|SKIP)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently TestNG provides the following two ways in which one can intercept test or config executions
Today TestNG does not distinguish between a successful invocation vs a wilful skip of invoking the callback and so if a user within their
run()
implementation, decided to never patch through the callback, TestNG would still classify that method as passed.More details can be found here #2700 (review)
This issue is to track this discrepancy and arrive at a proper solution.
The text was updated successfully, but these errors were encountered: