-
Notifications
You must be signed in to change notification settings - Fork 143
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
Clean up/complete tests #6
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
@m-reza-rahman this can be close. After I'll do some test with the embedded we can discuss again about adding it or not |
To be honest, our tests are very inadequate for a reference project. We definitely need to improve that. However, this can be done after the Jakarta EE 9 release. Reza Rahman Please note views expressed here are my own as an individual community member and do not reflect the views of my employer. |
Looks like Arquillian now supports JUnit 5. We should upgrade when we can. Reza Rahman Please note views expressed here are my own as an individual community member and do not reflect the views of my employer. |
@m-reza-rahman and @glassfishrobot, What are the deliverables for this, would we need to adopt junit 5 style in integration tests and adding JMeter tests for stress testing etc. I can take this up but would need some help. |
We cannot upgrade to JUnit 5 until the Jakarta EE 10 update is done. There is a separate issue for that. Similarly, there is a separate issue for JMeter. There are two aspects of the work on this issue:
Note that while I can offer some help, this is not a simple task by any stretch of the imagination. It requires a very self motivated individual with a relatively high proficiency level. I would say in academic terms, this is for someone that routinely gets A+’s on their 200/300 level CS courses. There is simpler work to pick up. |
Looks like JUnit 5 support is in, can this be closed or is it more a case of adding more tests for functional gaps? I can try to run the jacoco coverage tests if that would help |
There are huge gaps. I would say our coverage is maybe 5-10%. Someone needs to analyze carefully and chart out how we sensibly improve test coverage. |
~25% is a lot higher than what I thought. As I said though, we really can't rely on these tests for stability/regression. It'll probably be a very long time before we can. This is an area where longer term contribution from at least one dedicated person would really help. |
Integrate Arquillian/GlassFish Embedded/Weld EE/Weld SE as needed.
The text was updated successfully, but these errors were encountered: