> pry --help Usage: pry [options] [testfilter] Options: --version show program's version number and exit -h, --help show this help message and exit -c, --clear Clear all .pyc and .pyo files in the project base and included paths before run. -l, --list List all tests. -r, --recurse Recurse through child directories. -s, --stats Print coverage summary. -n BENCHMARK, --benchmark=BENCHMARK Run each test N times. -q, --quiet Quiet. -v, --verbose Increase verbosity. Can be passed multiple times. --debug-dump For debugging only. Like -l, but dump the full tree structure. Profiling: Generating run profiles for unit tests. -p, --profile Do a profiling run. Usually used in conjunction with -n to specify multiple runs. --profile-sort=PROFILE_SORT Profile result sorting key. See Python documentation for pstats module.
The optional test filter that can be specified to pry operates as follows:
First, all tests in the current directory are loaded (recursively if the -r flag is specified).
Then, the filter is applied to select a subset of tests based on a partial match strategy.
The following examples illustrate the process (commands are run in the examples subdirectory):
> pry -l ./test_autotree MyContainer test_one test_two ./test_basic MySuite test_one test_three test_two ./test_profile ProfTest test_one ./test_trees MyContainer test_one test_two Total: 8
> pry -l test_basic ./test_basic MySuite test_one test_three test_two Total: 3
> pry -l test_one ./test_autotree MyContainer test_one ./test_basic MySuite test_one ./test_profile ProfTest test_one ./test_trees MyContainer test_one Total: 4
> pry -l ProfTest.test_one ./test_profile ProfTest test_one Total: 1
Copyright Nullcube 2008