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
During the development of the TCK for Jakarta EE 10 there was no clear direction from the Jakarta Platform TCK on whether or not there would be a standard test framework to be used for Standalone TCKs (Junit4, Junit5, vs. TestNG).
When porting the TCK we decided to use TestNG to have a similar structure to other standalone TCKs that existed at the time.
For Jakarta EE 11 Junit5 is going to be the preferred test framework, so we will need to do some refactoring.
During the development of the TCK for Jakarta EE 10 there was no clear direction from the Jakarta Platform TCK on whether or not there would be a standard test framework to be used for Standalone TCKs (Junit4, Junit5, vs. TestNG).
When porting the TCK we decided to use TestNG to have a similar structure to other standalone TCKs that existed at the time.
For Jakarta EE 11 Junit5 is going to be the preferred test framework, so we will need to do some refactoring.
Now that we have some standards to follow we should get our TCK up to date with what all the other specs are expected to do: https://github.com/jakartaee/platform-tck/wiki/Standard-Rules-while-separating-standalone-TCKs-from-platform-TCK
The text was updated successfully, but these errors were encountered: