Exclude untestable code from coverage #2172
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #
Code Changes
pragma: no cover
toif __name__ == "__main__:"
codeSteps to Confirm
pytest tests/ctl -m "unit"
and verifymigrations
andif __name__ == "__main__:"
sections are not included in theterm-missing
sectionPre-Merge Checklist
CHANGELOG.md
Description Of Changes
In thinking about #2135 I am adding some exclusions from coverage here. The
migrations
are used by alembic and not by fides code directly, the only reason we have them in a directory under coverage is so plus can access them.We could probably jump through some hoops and find a way to test the
if __name__ == "__main__:"
sections, but doing so would be for the sake of coverage and not meaningful.