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

Audit unit test coverage #17

Open
arschles opened this issue Mar 23, 2016 · 6 comments
Open

Audit unit test coverage #17

arschles opened this issue Mar 23, 2016 · 6 comments

Comments

@arschles
Copy link
Member

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.

@arschles arschles added this to the v2.0-rc1 milestone Mar 23, 2016
@jackfrancis jackfrancis modified the milestones: v2.0-beta3, v2.0-rc1 Apr 18, 2016
@jackfrancis
Copy link
Member

jackfrancis commented Apr 18, 2016

At the very least this issue will include bringing server_test.go.TestPostClusters up to speed with the standard idiom for this project. Don't use that as an excuse not to increase overall coverage!

@jackfrancis jackfrancis self-assigned this Apr 18, 2016
@jackfrancis
Copy link
Member

Update make test to include the -cover option so we can track coverage over time.

@arschles
Copy link
Member Author

punting this to beta4

@arschles arschles modified the milestones: v2.0-beta4, v2.0-beta3 Apr 25, 2016
@arschles
Copy link
Member Author

arschles commented May 9, 2016

Moving this to RC1

@arschles arschles modified the milestones: v2.0-rc1, v2.0-beta4 May 9, 2016
@arschles
Copy link
Member Author

arschles commented May 9, 2016

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.

@arschles arschles modified the milestone: v2.0-rc1 May 19, 2016
@jackfrancis jackfrancis changed the title Increase unit test coverage Audit unit test coverage Jun 12, 2016
@jackfrancis
Copy link
Member

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.

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

No branches or pull requests

3 participants