Message110381
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 are requirements for the old test_support.run_unittest code to reach unittest compatibility? Can't you just deprecate test_support.run_unittest() so maintainers get signal to upgrade their tests suite? Then the upgrade happen faster.
P.S. I do not need many plugin use cases right now. The test suite tools are often separated into three components - test discovery, test runner and test formatting, but that's all. |
|
Date |
User |
Action |
Args |
2010-07-15 17:00:43 | techtonik | set | recipients:
+ techtonik, exarkun, pitrou, giampaolo.rodola, r.david.murray, michael.foord |
2010-07-15 17:00:43 | techtonik | set | messageid: <1279213243.29.0.523340423328.issue9028@psf.upfronthosting.co.za> |
2010-07-15 17:00:41 | techtonik | link | issue9028 messages |
2010-07-15 17:00:40 | techtonik | create | |
|