"make tests" should ignore externally set $COVERAGE_FILE

Issue #15 wontfix
Geoff Bache created an issue

I have set $COVERAGE_FILE to a global location in my shell startup script. On running the tests with "make tests" quite a few of them failed and I got strange information added to my global coverage file. When I unset the variable they work, of course...

Comments (2)

  1. Ned Batchelder repo owner

    I'm not sure it's reasonable to expect all projects to run within the same environment. If you are running coverage.py tests, I think it's OK to have an expectation that the environment will be appropriate for running coverage.py tests.

  2. Log in to comment