-
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
Remove deprecated JUnit related support in TestNG #3022
Comments
That's to say, the Junit4 Testcase will not running with TestNG 7.10.0~. should Junit5 work well with TestNG latest version. |
@bobshie Yes. With https://github.com/junit-team/testng-engine JUnit5 should be able to run JUnit4, JUnit5 et TestNG test cases together. Please share your experience on testng-engine if something is not working as expected. |
Hello, We have Junit4 test cases that based on Junit4, but after we uplift testng to 7.10.2, these test cases aren't running. I changed the dependent from
to
then it works.
|
TestNG Version
7.9.0
Expected behavior
TestNG need not support JUnit anymore now.
Actual behavior
Is the issue reproducible on runner?
JUnit3/JUnit4 support in TestNG was deprecated as of
v7.7.0
. This was done because the JUnit team have enhanced JUnit5 to support running TestNG using JUnit itself. So there's no need for TestNG to do the reverse of this and TestNG users can switch over to using JUnit5 if they have a mixture of JUnit and TestNG tests and need both of them to be executed by the same test runner (JUnit5 would be the driver which would internally invoke TestNG)For more details please refer to the official documentation of the testng-engine by JUnit at https://github.com/junit-team/testng-engine
The text was updated successfully, but these errors were encountered: