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.

Sign up for GitHub

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

Jump to bottom

is test coverage sufficient? #114

Closed
barmintor opened this issue Jun 18, 2018 · 1 comment
Closed

is test coverage sufficient? #114

barmintor opened this issue Jun 18, 2018 · 1 comment
Assignees
@jcoyne

Comments

@barmintor
Copy link
Member

A requirement for being in the Samvera organization is: Good unit test coverage measured by community (e.g. 100% or 75% of what’s important)

As this hasn't been defined, we in the Core Component Maintenance Working Group would like to ask the product owner if you or any developers who work on this project know if they feel like the coverage is sufficient on this project to be confident in continuing work on it? If not, we encourage you to create an issue to increase test coverage and add the maintenance label. If so, please close this issue.

Thanks!
@tpendragon
Copy link
Contributor

The project is currently at 99%, which seems likely to be sufficient. If the product owner (@jcoyne) feels like it would be useful for us to try to get it higher please make a ticket with the maintenance label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcoyne jcoyne

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jcoyne @barmintor @tpendragon