[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Ned Batchelder added the comment: Whoever takes this up next: let me know if I can help. -- ___ Python tracker ___

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Changes by Brett Cannon : -- assignee: brett.cannon -> ___ Python tracker ___ ___

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Brett Cannon added the comment: Just an FYI that I have never managed to make this work. -- ___ Python tracker ___

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Changes by Brett Cannon : -- pull_requests: +1948 ___ Python tracker ___ ___

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Changes by Brett Cannon : -- assignee: -> brett.cannon ___ Python tracker ___ ___

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Brett Cannon added the comment: I learned a few thing trying to make this work. One is that the COVERAGE_PROCESS_START does need to point to an actual .ini file (which includes an empty file). Two,

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Brett Cannon added the comment: There's also what changes might occur in the coverage results when we start using fullcoverage: https://github.com/python/core-workflow/issues/18 -- ___ Python tracker

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Nick Coghlan added the comment: To be more specific regarding `sitecustomize.py`: $ echo "print('Hello from sitecustomize.py')" > Lib/sitecustomize.py $ ./python -c "print('Hello from command line')" Hello from sitecustomize.py Hello from command line Since we only need these

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Nick Coghlan added the comment: As a starting point, I'd suggest looking at what can be achieved without making any changes to CPython or its test suite: 1. Set COVERAGE_PROCESS_START in the environment where the tests are being run 2. Inject a sitecustomize.py file into Lib (and add

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

Jaysinh shukla added the comment: I found the regrtest wasn't displaying correct coverage for when the code is executed from call `Lib.test.support.script_helper.assert_python_ok`. I found `assert_python_ok` is using `subprocess` under the hood. It seems this problem is unobserved from a long

[issue11978] Report correct coverage.py data for tests that invoke subprocesses

New submission from Nick Coghlan ncogh...@gmail.com: http://nedbatchelder.com/code/coverage/subprocess.html describes how to instruct a test suite that spawns subprocesses to correctly report coverage data for code covered only in those subprocesses. regrtest currently doesn't do this, so