Added coverage metric and set current coverage as a baseline. This should protect the codebase from merging uncovered changes.
Motivation and Context
Currently, the codebase doesn't have a measure of test coverage. For a public library, it's important to track the coverage and avoid merging new code which is not properly tested
How has this been tested?
Tested by running all tests on the projects
Screenshots (if appropriate):
Types of changes
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
atapin
commented
1 month ago
Description
Added coverage metric and set current coverage as a baseline. This should protect the codebase from merging uncovered changes.
Motivation and Context
Currently, the codebase doesn't have a measure of test coverage. For a public library, it's important to track the coverage and avoid merging new code which is not properly tested
How has this been tested?
Tested by running all tests on the projects
Screenshots (if appropriate):
Types of changes
Checklist: