Michael Foord added the comment:
This is only an issue if a test package pollutes its environment without
cleaning up (puts mocks in place that it doesn't remove for example). Fixing
this would require discover to use multiple processes to run tests, which isn't
going to happen (at least not s
Éric Araujo added the comment:
> imports from previous unittests corrupt the namespace of subsequent unittests
> and lead to failures
> (usually if there are mock objects in previously imported unit tests)
Can you tell more about this? I haven’t run into this issue with large test
suites that
New submission from the mulhern:
You can run "python -m unittest discover " and the unittests
discovered by discover will be run. This is nice.
However, it is actually desirable to run each unittest package individually,
rather than in the same interpreter instance. When run via discover, impo
