Message 129176 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	blokeley
Recipients	blokeley, docs@python
Date	2011-02-23.11:42:52
SpamBayes Score	0.001330081
Marked as misclassified	No
Message-id	<1298461373.56.0.0867432714067.issue11298@psf.upfronthosting.co.za>
In-reply-to

Content
`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

`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

History
Date	User	Action	Args
2011-02-23 11:42:53	blokeley	set	recipients: + blokeley, docs@python
2011-02-23 11:42:53	blokeley	set	messageid: <1298461373.56.0.0867432714067.issue11298@psf.upfronthosting.co.za>
2011-02-23 11:42:52	blokeley	link	issue11298 messages
2011-02-23 11:42:52	blokeley	create