Can't use "coverage run -m unittest discover" if tests are in a "test" directory

[nedbat]

Although "python -m unittest discover" will properly run tests in a "test" directory, "coverage run -m unittest discover" will not. This is because "coverage run -m" will put the unittest directory into the sys,path, and that directory has a "test" subdirectory. The tests are discovered in the product's test directory, but when the time comes to import them, the unittest "test" directory is examined for them instead, where they do not exist, and the import fails.

---

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/155

[nedbat]

An extra element in sys.path meant that "test.test_foo" modules weren't found because they were sought in unittest.test. Fixed in <<changeset 781082764b17 (bb)>>.