Code review comment for lp:~james-w/subunit/discovery

Revision history for this message
James Westby (james-w) wrote :

On Mon, 14 Jun 2010 08:58:22 -0000, Robert Collins <email address hidden> wrote:
> Review: Needs Fixing
> Very nice except that the help is now the testtools help, and it really should mention that it will be outputting subunit ;).

Have a look at it now.

python -m subunit.run --asdf
option --asdf not recognized
Usage: run.py [options] [tests]

Options:
  -h, --help Show this message
  -v, --verbose Verbose output
  -q, --quiet Minimal output
  -f, --failfast Stop on first failure
  -c, --catch Catch control-C and display results
  -b, --buffer Buffer stdout and stderr during test runs

Examples:
  run.py test_module - run tests from test_module
  run.py module.TestClass - run tests from module.TestClass
  run.py module.Class.test_method - run specified test method

[tests] can be a list of any number of test modules, classes and test
methods.

Alternative Usage: run.py discover [options]

Options:
  -v, --verbose Verbose output
  -f, --failfast Stop on first failure
  -c, --catch Catch control-C and display results
  -b, --buffer Buffer stdout and stderr during test runs
  -s directory Directory to start discovery ('.' default)
  -p pattern Pattern to match test files ('test*.py' default)
  -t directory Top level directory of project (default to
                   start directory)

For test discovery all test modules must be importable from the top
level directory of the project.

The output will be in subunit format.

Thanks,

James

« Back to merge proposal