Skip to content
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

Closed
krmahadevan opened this issue Jan 4, 2022 · 0 comments · Fixed by #2713
Closed

IHookable and IConfigurable callback discrepancy #2704

krmahadevan opened this issue Jan 4, 2022 · 0 comments · Fixed by #2713
Labels
Milestone

Comments

@krmahadevan
Copy link
Member

Currently TestNG provides the following two ways in which one can intercept test or config executions

  • IHookable
  • IConfigurable

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.

@krmahadevan krmahadevan added this to the 7.6.0 milestone Jan 7, 2022
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)
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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant