[New-bugs-announce] [issue11298] unittest discovery needs better explanation
report at bugs.python.org
Wed Feb 23 12:42:53 CET 2011
New submission from blokeley <blokeley at gmail.com>:
`python -m unittest discover` caught me out.
I had a test module called `test-foo.py` and no test was loaded.
When I renamed to `test_foo.py` it worked.
The documentation says "For a project’s tests to be compatible with test discovery they must all be importable".
I didn't realise that test-foo would not be importable. Could the documentation say "For a project’s tests to be compatible with test discovery they must all be importable, so ensure that the module names are valid Python identifiers."
Stackoverflow question is here: http://stackoverflow.com/questions/5088960/python-unittest-discovery-does-not-discover-tests
assignee: docs at python
nosy: blokeley, docs at python
title: unittest discovery needs better explanation
versions: Python 2.7, Python 3.2, Python 3.3
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce