You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
add coverage reporting to our automated testing suite
identify and prioritize functionality that's uncovered and thus untested
start adding tests for that functionality in order of priority
The text was updated successfully, but these errors were encountered:
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:
The text was updated successfully, but these errors were encountered: