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

Identify untested portions of the codebase #279

Closed
jardinetsouffleton opened this issue Nov 3, 2022 · 1 comment
Closed

Identify untested portions of the codebase #279

jardinetsouffleton opened this issue Nov 3, 2022 · 1 comment

Comments

@jardinetsouffleton
Copy link
Member

jardinetsouffleton commented Nov 3, 2022

As of now, our code coverage stands around 68%. While this is acceptable, we would benefit from understanding which portions of the codebase are lacking in terms of code coverage. This would allow us to have data on the current state of our code coverage and focus our efforts on most important sections.
Detailed coverage data available here

@jardinetsouffleton
Copy link
Member Author

jardinetsouffleton commented Nov 8, 2022

Lacking sections were identified and issues #285 #284 and #283 were created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant