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

Use code coverage to identify, address testing gaps #65

Open
falquaddoomi opened this issue Nov 12, 2024 · 0 comments
Open

Use code coverage to identify, address testing gaps #65

falquaddoomi opened this issue Nov 12, 2024 · 0 comments
Assignees

Comments

@falquaddoomi
Copy link
Collaborator

As @d33bs mentioned in #60 (comment), our code coverage in specific modules (e.g., models.py) is low. While I would recommend against writing tests simply to increase code coverage, I agree that the lack of coverage indicate parts of the code that are untested, and if they intersect important functionality then we should definitely write tests for that functionality.

At a high level, I think we should:

  1. add coverage reporting to our automated testing suite
  2. identify and prioritize functionality that's uncovered and thus untested
  3. start adding tests for that functionality in order of priority
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