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 porting of the Concurrency TCK for Jakarta EE 10 there had been no standards to follow.
I decided to follow the MicroProfile structure of using TestNG and Arquillian.
It has been noted by both the Jakarta EE and MP communities that Arquillian on TestNG has a major bug: arquillian/arquillian-core#395
Furthermore, we have seen that most Jakarta EE projects chose to use Junit instead of TestNG.
Main improvement
For 3.1, we should consider refactoring to use JUnit5 and Arquillian.
Other possible improvements:
Simplify testing based on the profile (web, full)
Automate the inclusion of framework / common packages for easier maintenance.
During the porting of the Concurrency TCK for Jakarta EE 10 there had been no standards to follow.
I decided to follow the MicroProfile structure of using TestNG and Arquillian.
It has been noted by both the Jakarta EE and MP communities that Arquillian on TestNG has a major bug: arquillian/arquillian-core#395
Furthermore, we have seen that most Jakarta EE projects chose to use Junit instead of TestNG.
Main improvement
Other possible improvements:
I'm also open to other suggestions on how we can make the TCK easier to understand and use.
The text was updated successfully, but these errors were encountered: