Simplify subprocess coverage setup #453
Comments
mih
added a commit
to mih/datalad-next
that referenced
this issue
Sep 28, 2023
The previous setup was taken from datalad-core. It comes from a time before `pytest`. With `pytest-cov` none of this complexity should be needed anymore. A similar setup has been implemented as part of datalad/datalad-ria#6 Closes datalad#453
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use the setup from datalad core here.
However, it turns out that almost none of that is needed, and pytest-cov does almost everything out of the box.
See datalad/datalad-ria#6 for a demo on what is neeed for adding subprocess coverage.
One thing to keep in mind when exploring coverage capture for special remote processes: We may never be able to get full coverage for "abnormal" exits. When git-annex externally terminates a special remote process, it seems "expected" that the
onexithandlers that coverage reporting relies on, do not reliably run.The text was updated successfully, but these errors were encountered: