[issue9028] test_support.run_unittest cmdline options and arguments

Éric Araujo added the comment: Closing again, following Michael’s comment. Re: run_unittest, it’s a very small function mostly obsolete now, I don’t think there are compat rules. Just don’t use it. -- nosy: +eric.araujo status: open -> closed ___

[issue9028] test_support.run_unittest cmdline options and arguments

anatoly techtonik added the comment: s/need/have/ -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue9028] test_support.run_unittest cmdline options and arguments

anatoly techtonik added the comment: Cool, unittest.main() worked for me, but I still lack the introspection to see what tests are available inside the file. Would there be any objections against quickly adding -l, --list option to expose the result of test discovery as it works now? What ar

[issue9028] test_support.run_unittest cmdline options and arguments

Michael Foord added the comment: Right. That code should change. My intention is to go through the whole of the Python test suite and make them compatible with the new unittest features. I also intend to add extensions to unittest to allow listing of collecting tests and filtering tests by na

[issue9028] test_support.run_unittest cmdline options and arguments

anatoly techtonik added the comment: > If you use Python 2.7 then the following at the end of the test module > enables the same command line features that David Murray pointed you to: > > if __name__ == '__main__': >    unittest.main() Unfortunately, test_httpservers.py from stdlib contains t

[issue9028] test_support.run_unittest cmdline options and arguments

Michael Foord added the comment: """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 ... """ If you use Python 2.7 then the following at the end of the test module enab

[issue9028] test_support.run_unittest cmdline options and arguments

anatoly techtonik added the comment: 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 what

[issue9028] test_support.run_unittest cmdline options and arguments

Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue9028] test_support.run_unittest cmdline options and arguments

R. David Murray added the comment: Yes, running individual tests has already been implemented as part of unittest (where it belongs): ./python -m unittest test.test_httpservers.BaseHTTPServerTestCase.test_handler . -- Ran 1 te

[issue9028] test_support.run_unittest cmdline options and arguments

Jean-Paul Calderone added the comment: These sound more like features for the unittest runner (one of which is implemented already). Also, please don't propagate "::" as a namespace separator in Python. That's what "." is for. -- nosy: +exarkun _

[issue9028] test_support.run_unittest cmdline options and arguments

anatoly techtonik added the comment: Damn. I still failed to forge last use case. In should of course read: > python test_httpservers.py CGIHTTPServer::url_collapse_path_split CGIHTTPServer::url_collapse_path_split ... ok Wave develops bad habits. -- _

[issue9028] test_support.run_unittest cmdline options and arguments

New submission from anatoly techtonik : Need --help, --list options and TestSute::testcase args for test_support.run_unittest User story: I am covering CGIHTTPServer with tests according to http://www.rfc-editor.org/rfc/rfc3875.txt speccy and want to run a single test in a cycle. I am runnin