#13025 closed (wontfix)
Test runner should print failed test path in format that is accepted by `manage.py test ...`
Reported by: | Piotr Czachur | Owned by: | nobody |
---|---|---|---|
Component: | Testing framework | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When I run all test and some of them fail I see
FAIL: "test_function_name (projectname.appname.tests.TestCaseName)".
Now when I want to run this single test (which happens very often) I need to manualy compose parameter for manage.py test
like this:
manage.py test appname.TestCaseName.test_function_name
It would be handy if test runner printed failed test path, that can be directly used for manage.py test
:
FAIL: test_function_name (appname.TestCaseName.test_function_name)
Change History (2)
comment:1 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 by , 15 years ago
Got your point - finding test is easier having full path, which is obviously true, but why test runner takes incompatible argument appname.TestCaseName.test_function_name? Wouldn't it be more convenient for test runner to take param like projectname.appname.tests.TestCaseName.test_function_name? Pasting text is better than manually writing, because you avoid typos ans save precious time.
I'm going to close this wontfix - I can see what you're driving at, but there is a legitimate use for having the full class there - so you can actually find the test definition. This is also helpful if the test class names are ambiguous.
Composing the actual test name isn't that hard once you have the full class name, so I'd rather stick to the fully qualified name.