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

TCK Improvements for 3.1 #269

Closed
4 tasks done
KyleAure opened this issue Jan 10, 2023 · 0 comments · Fixed by #332
Closed
4 tasks done

TCK Improvements for 3.1 #269

KyleAure opened this issue Jan 10, 2023 · 0 comments · Fixed by #332
Assignees
Labels
EE11 Suggested changes for Jakarta EE 11 TCK
Milestone

Comments

@KyleAure
Copy link
Contributor

KyleAure commented Jan 10, 2023

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:

I'm also open to other suggestions on how we can make the TCK easier to understand and use.

@KyleAure KyleAure added TCK EE11 Suggested changes for Jakarta EE 11 labels Jan 10, 2023
@KyleAure KyleAure self-assigned this Jan 10, 2023
@KyleAure KyleAure added this to the 3.1 milestone Jan 10, 2023
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