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

test coverage #42

Closed
danieleades opened this issue Mar 21, 2020 · 0 comments · Fixed by #37
Closed

test coverage #42

danieleades opened this issue Mar 21, 2020 · 0 comments · Fixed by #37
Labels
C-tests Category: Testing

Comments

@danieleades
Copy link
Contributor

This crate currently has zero test coverage

This makes refactoring and continuous integration impossible.
It also makes it extremely difficult to support community contributions

Perhaps an incremental approach is best? Start tracking test coverage, then insist that each pull request going forward either improve test coverage, or at least not significantly degrade it.
@danieleades danieleades mentioned this issue Mar 21, 2020
Merged
@Hirevo Hirevo added the C-tests Category: Testing label Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-tests Category: Testing
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add test coverage CI and badge danieleades/alexandrie
2 participants
@Hirevo @danieleades