ANN: Testoob 1.15 released

O

oripel

Testoob is the advanced Python test runner and testing framework that
spices up any existing unittest test suite.

Home: http://code.google.com/p/testoob

Version 1.15 (Oct. 2009) adds better Python 2.6, IronPython, and
Jython support, as well as test coverage improvements, better color
support, and some new options and bugfixes. *nix and Windows are fully
supported.

Installation options:
* 'easy_install -U testoob'
* One of the packages at http://code.google.com/p/testoob/downloads/list

This version wouldn't have been possible without the help of Ronnie
van 't Westeinde.
 
J

Jorgen Grahn

Testoob is the advanced Python test runner and testing framework that
spices up any existing unittest test suite.

Home: http://code.google.com/p/testoob

But this sentence on the home page

The documentation is sadly outdated, but may be
a starting point:

made me stop looking. As far as I can tell, you cannot even find out
what's so advanced about it (or why "advanced" is a good thing)
without starting to use it. A brief comparison with module unittest
(which I am rather unhappy with) would have been nice, too.

/Jorgen
 
O

oripel

But this sentence on the home page

    The documentation is sadly outdated, but may be
    a starting point:

made me stop looking.  As far as I can tell, you cannot even find out
what's so advanced about it (or why "advanced" is a good thing)
without starting to use it.  A brief comparison with module unittest
(which I am rather unhappy with) would have been nice, too.

Those are good points Jorgen, thanks.

The briefest summary I would give is:
(a) You can run your unittest suites unmodified (so it's easy to try
out)
(b) The test running options have the potential to whet your appetite:

% testoob -h
Usage
=====
testoob [options] [test1 [test2 [...]]]

examples:
testoob - run default set of tests
testoob MyTestSuite - run suite 'MyTestSuite'
testoob MyTestCase.testSomething - run MyTestCase.testSomething
testoob MyTestCase - run all 'test*' test methods in
MyTestCase

Options
=======
--version show program's version number and exit
--help, -h show this help message and exit
--bgcolor=WHEN What's the background color of the
terminal.
This is used to determine a readable
warning
color. Choices are ['auto', 'light',
'dark'],
default is 'auto'
--color-mode=WHEN When should output be in color? Choices
are
['never', 'always', 'auto'], default is
'auto'
--glob=PATTERN Filtering glob pattern
--html=FILE output results in HTML
--immediate, -i Immediate feedback about exceptions
--list, -l List the test classes and methods found
--list-formatted=FORMATTER Like option '-l', just formatted (e.g.
csv).
--pbar Show a progress bar
--pdf=FILE output results in PDF (requires
ReportLab)
--processes=NUM_PROCESSES Run in multiple processes, use Pyro if
available
--processes_pyro=NUM_PROCESSES
Run in multiple processes, requires Pyro
--processes_old=NUM_PROCESSES
Run in multiple processes, old
implementation
--randomize-order Randomize the test order
--randomize-seed=SEED Seed for randomizing the test order,
implies
--randomize-order
--regex=REGEX Filtering regular expression
--repeat=NUM_TIMES Repeat each test
--silent, -s no output to terminal
--timed-repeat=SECONDS Repeat each test, for a limited time
--time-each-test Report the total time for each test
--xml=FILE output results in XML
--quiet, -q Minimal output
--verbose, -v Verbose output
--vassert Make asserts verbose
--interval=SECONDS Add interval between tests
--timeout=SECONDS Fail test if passes timeout
--timeout-with-threads=SECONDS
Fail test if passes timeout, implemented
with
threads
--stop-on-fail Stop tests on first failure
--debug Run pdb on tests that fail
--threads=NUM_THREADS Run in a threadpool
--capture Capture the output of the test, and show
it only
if test fails
--coverage=AMOUNT Test the coverage of the tested code,
choices
are: ['silent', 'slim', 'normal',
'massive',
'xml']
--test-method-glob=PATTERN Collect test methods based on a glob
pattern
--test-method-regex=REGEX Collect test methods based on a regular
expression
--profiler=PROFILER Profile the tests with a profiler,
choices are:
['hotshot', 'profile']
--profdata=FILE Target file for profiling information,
default
is 'testoob.stats'
--rerun-on-fail Used with --debug, rerun a failing test
when
debugging it


- orip
 
J

Jorgen Grahn

But this sentence on the home page

    The documentation is sadly outdated, but may be
    a starting point:

made me stop looking.  As far as I can tell, you cannot even find out
what's so advanced about it (or why "advanced" is a good thing)
without starting to use it.  A brief comparison with module unittest
(which I am rather unhappy with) would have been nice, too.

Those are good points Jorgen, thanks.

The briefest summary I would give is:
(a) You can run your unittest suites unmodified (so it's easy to try
out)
(b) The test running options have the potential to whet your appetite:

% testoob -h
Usage
=====
testoob [options] [test1 [test2 [...]]]

examples:
testoob - run default set of tests
testoob MyTestSuite - run suite 'MyTestSuite'
testoob MyTestCase.testSomething - run MyTestCase.testSomething
testoob MyTestCase - run all 'test*' test methods in
MyTestCase

Options
=======
[dozens of options snipped]

Oh, good. Both (a) and (b) are certainly good info for the web page.

Many of the options are for transforming the output -- something I
prefer (as a Unix guy) to do myself with a filtering script I have
control over. Others will like it though, and I like some of the other
options -- especially the one which lists all tests, and the "run
tests which match this string" option.

/Jorgen
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,184
Messages
2,570,978
Members
47,578
Latest member
LC_06

Latest Threads

Top