-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Improve code coverage #20
Labels
Comments
This was referenced May 11, 2018
This was referenced Jul 5, 2018
The codecov badge says 50% today! :-) |
Currently at 59%, but it should definitely improve. Maybe a good candidate for our OC1 Hackergarten. |
Yes, it is not a killer criteria but certainly a low hanging fruit. Could be combined e.g. with increasing the use of Hamcrest where appropriate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The code coverage is currently 40%, see codecov badge. We should create more JUnit tests especially in packages with a very low coverage. At least 60% like the JSR 363 RI should be archived, if more, even better.
The text was updated successfully, but these errors were encountered: