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

Refactor TCK to use JUnit 5 #277

Closed
KyleAure opened this issue May 3, 2023 · 0 comments · Fixed by #279
Closed

Refactor TCK to use JUnit 5 #277

KyleAure opened this issue May 3, 2023 · 0 comments · Fixed by #279
Assignees
Labels
EE11 Suggested changes for Jakarta EE 11 TCK

Comments

@KyleAure
Copy link
Contributor

KyleAure commented May 3, 2023

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

@KyleAure KyleAure added TCK EE11 Suggested changes for Jakarta EE 11 labels May 3, 2023
@KyleAure KyleAure self-assigned this May 3, 2023
@KyleAure KyleAure mentioned this issue Jun 1, 2023
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EE11 Suggested changes for Jakarta EE 11 TCK
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant