Originally reported by Pedro Algarvio (Bitbucket: s0undt3ch, GitHub: s0undt3ch)
When checking coverage using "coverage run" consider injecting a COVERAGE_ environment variable.
This would allow detecting that the code is being covered and proceed acroding to that information.
For example, to speed up tests I often just kill any subprocesses spawned instead of terminating them(yes we spawn a lot of processes and it does make a huge difference), however, this results in the coverage data not being written.
Should I provide a PR?
Maybe COVERAGE_COMMAND, which in this case would be set to run?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4