-
Notifications
You must be signed in to change notification settings - Fork 0
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
Audit unit test coverage #17
Comments
At the very least this issue will include bringing |
Update |
punting this to beta4 |
Moving this to RC1 |
Also note that test coverage has been significantly increased as the codebase has grown. We'll need to check the coverage again. I hope we can close this pretty early in the RC1 cycle. |
I've changed this ticket to "Audit unit test coverage", as the project has progressed enough that we'll want to target unit test coverage more explicitly. The objective of this ticket is to "componentize" missing unit test coverage areas, and to create specific issues to improve unit test coverage in particular areas of code so that the scope doesn't become overwhelming, and is easy to distribute among multiple contributors. |
As of this writing, coverage is just over 50%. We should intelligently look for ways to increase it, then write the tests to do so.
The text was updated successfully, but these errors were encountered: