[issue15007] Unittest CLI does not support test packages very well

Changes by Ezio Melotti : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue15007] Unittest CLI does not support test packages very well

Changes by Éric Araujo : -- nosy: +eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue15007] Unittest CLI does not support test packages very well

R. David Murray added the comment: Right, I'm not wanting to run discovery from the command line, I'm wanting to run the tests in the package by package name. In my mind, this is exactly parallel to specifying a module name and having unittest automatically discover the TestCase classes in i

[issue15007] Unittest CLI does not support test packages very well

Michael Foord added the comment: Whilst I agree in principle... The trouble is that when you do this: python -m unittest test_pk What you are saying is "run all the tests from the test_pk module". You *aren't* launching discovery. This should work: python -m unittest discover -t .

[issue15007] Unittest CLI does not support test packages very well

New submission from R. David Murray : Suppose you have a test package: test_pkg __init__.py test_mytest.py If __init__.py is empty and you run python -m unittest test_pk no tests are found. You can get this to work by adding the following boiler plate to __init__.py: def lo