Created on 2010-12-04 00:20 by michael.foord, last changed 2011-01-03 18:19 by michael.foord. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg123309 - (view) | Author: Michael Foord (michael.foord) *  |
Date: 2010-12-04 00:20 | |
Feature request against unittest2. Issue 18: https://code.google.com/p/unittest-ext/issues/detail?id=18 As providing a file path instead of module name to the unittest command line runner currently fails there is no backwards compatibility issue with making this work. The only potential issue is if a test suite or module is genuinely 'foo.py' then we could end up attempting to load the file instead of the specified suite / module. To get round this we should only attempt to load tests from a file by checking the file exists first. The specified still needs to be *imported* to load tests from it, so the file path will be converted to a module name by replacing path separators with '.'. The way to execute test files that aren't importable as modules is to execute them directly not using `python -m unittest`. |
|||
| msg123310 - (view) | Author: Michael Foord (michael.foord) * |
Date: 2010-12-04 01:12 | |
Committed revision 87003. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-01-03 18:19:56 | michael.foord | set | status: open -> closed |
| 2010-12-04 01:12:26 | michael.foord | set | resolution: fixed messages: + msg123310 stage: resolved |
| 2010-12-04 00:32:18 | merwok | set | nosy:
+ merwok |
| 2010-12-04 00:20:06 | michael.foord | create | |