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 techtonik
Recipients exarkun, giampaolo.rodola, michael.foord, pitrou, r.david.murray, techtonik
Date 2010-06-20.19:51:47
SpamBayes Score 0.04977587
Marked as misclassified No
Message-id <1277063510.09.0.986638526039.issue9028@psf.upfronthosting.co.za>
In-reply-to
Content
RDM, running your way will execute test from standard library location of installed Python.

> python -m unittest test.test_httpservers.BaseHTTPServerTestCase.test_handler

But I want to execute test from my own patched copy of test_httpservers.py with whatever python I want. I.e.

> C:\Python27\python.exe Z:\python-cgi-tests\test_httpservers.py ...

I prefer to explicitly specify it in command line to be sure that I execute the right test suite. I also don't feel like typing `-m unittest test.test_httpservers.` each time when there is shell completion, and every decent file manager has keyboard shortcuts for inserting active filename into command line prompt.

You know - I am not a core contributor to maintain a bunch of batch files for all kind of operations, so I am interested to make testing process more intuitive.

I know how "TestCase" and "test_" auto discovery works. The point is to remove the need in extra typing, because test runner can add these suffix/prefixes automatically when parsing command line.

@exarkun: Ok. `.` is fine - `::` was a copy paste from my old PHP test runner.
History
Date User Action Args
2010-06-20 19:51:50techtoniksetrecipients: + techtonik, exarkun, pitrou, giampaolo.rodola, r.david.murray, michael.foord
2010-06-20 19:51:50techtoniksetmessageid: <1277063510.09.0.986638526039.issue9028@psf.upfronthosting.co.za>
2010-06-20 19:51:48techtoniklinkissue9028 messages
2010-06-20 19:51:47techtonikcreate