[New-bugs-announce] [issue10620] `python -m uniittest` should work with file paths as well as test module names

[Michael Foord]

New submission from Michael Foord <michael at voidspace.org.uk>:

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`.

----------
assignee: michael.foord
components: Library (Lib)
messages: 123309
nosy: michael.foord
priority: normal
severity: normal
status: open
title: `python -m uniittest` should work with file paths as well as test module names
type: behavior
versions: Python 3.2, Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10620>
_______________________________________