-
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
After upgrading to TestNG 7.5.0, setting ITestResult.status to FAILURE
doesn't fail the test anymore
#2771
Comments
Can you please check in 7.6.0 which is the latest released version @asolntsev |
@krmahadevan Just tried: the problem still reproduced with TestNG 7.6.0 |
TestNG 7.5 and 7.6.0 have a bug testng-team/testng#2771 which break Selenide soft asserts. We may upgrade to a newer TestNG only when this issues gets fixed.
TestNG 7.5 and 7.6.0 have a bug testng-team/testng#2771 which break Selenide soft asserts. We may upgrade to a newer TestNG only when this issues gets fixed.
is it a result of this fix: #2558 ?
TestNG 7.4.0
|
@dr29bart Yes, it seems so. Generally, the idea to preserve the order of listeners is good. But still, TestNG own listeners should be executed AFTER all user-defined listeners (after test execution). |
Hi guys, any progress in this? Totally agree with @asolntsev. This issue affected all our unit tests. |
Hi guys ! |
@YaroslavBurlakaLS - We are working on adding a few more fixes before |
TestNG Version
Given
A project with Listener (my custom "soft assert" listener) which marks
ITestResult
status asFAILURE
after the test.Expected behavior
I expect my test to fail.
Actual behavior
After upgrading to TestNG 7.5, my test doesn't fail anymore. It's a bug.
Is the issue reproducible on runner?
Test case sample
Please check this trivial project which stabely reproduces the problem:
https://github.com/asolntsev/testng-listeners-sample
The text was updated successfully, but these errors were encountered: