codecov[bot]
commented
1 year ago Codecov Report
Patch and project coverage have no change.
Comparison is base (
7ccb5e9) 100.00% compared to head (d20738e) 100.00%.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## main #340 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 38 38 Lines 2502 2502 ========================================= Hits 2502 2502 ``` | Flag | Coverage Δ | | |---|---|---| | unittests | `100.00% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LSSTDESC#carryforward-flags-in-the-pull-request-comment) to find out more. Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LSSTDESC). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LSSTDESC):umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
This registers a new mark,
@pytest.mark.slow, that can be used to annotate test cases that are known to be slow and can be skipped for quick unit testing.The workflow is modified to first run any tests NOT marked with slow, and on success, run the remaining slow tests. The coverage from the two runs is combined, so this does not result in any change to overall test coverage.
Additional tests will be marked as slow in upcoming PRs, once later "fast" tests no longer rely on state produced by earlier "slow" tests.