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
Currently the test coverage on conda-store is minimal. This makes it difficult to identify when changes might have unintended consequences (like breaking some functionality in another part of the application). For example, it would be nice if issues like #615 could be caught by automated tests.
It would be nice to:
have more test coverage in conda-store
remove tests that are not helpful (if possible)
have the ability to see code coverage information for each pr (eg. integration with code cov, or a github action)
be able to run unit tests locally (eg. the unit tests are fast)
Value and/or benefit
This will give developers more confidence that their proposed changes will not have unintended consequences in other parts of the software.
we achieve most of the goals of this issue. Code coverage is at 75%
TOTAL 4168 1062 75%
I think there is still lots of room for improvements with the tests, but I think this is a good start. Will write new issues for other improvements that can be made.
Context
Currently the test coverage on conda-store is minimal. This makes it difficult to identify when changes might have unintended consequences (like breaking some functionality in another part of the application). For example, it would be nice if issues like #615 could be caught by automated tests.
It would be nice to:
Value and/or benefit
This will give developers more confidence that their proposed changes will not have unintended consequences in other parts of the software.
Anything else?
Currently the code coverage is:
The text was updated successfully, but these errors were encountered: