[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#825828: ITP: python-pinocchio -- set of extensions to the nose unit testing framework



Package: wnpp
Severity: wishlist
Owner: Gilles Dubuc <gilles@wikimedia.org>

* Package name    : python-pinocchio
  Version         : 0.4.2
  Upstream Author : C. Titus Brown and Michal Kwiatkowski
<titus@idyll.org,michal@trivas.pl>
* URL             : https://github.com/mkwiatkowski/pinocchio
* License         : MIT License
  Programming Lang: Python
  Description     : set of extensions to the nose unit testing framework

Pinocchio is a set of extensions to the nose unit testing framework for Python.

stopwatch -- selecting tests based on execution time

Sometimes your unit tests just seem to take forever. Well, now you can
get rid of the slow ones automatically!

The pinocchio.stopwatch extension module lets you time the unit tests
being run, and -- once times have been recorded -- then lets you
select only those that run faster than a given amount of time. As a
bonus, the test names and run times are stored in a simple format -- a
pickled dictionary -- so you can target specific tests for speedup,
too.

decorator -- adding attributes to tests

The attrib extension module for nose is a great way to select subsets
of tests based on attributes you've given the test functions, classes,
or methods. But what if you don't want to modify the source code to
add the attributes?

figleafsections -- find out what tests are executing which parts of your code

(You'll need to install figleaf to use this plugin; it will install
the figleaf package and the annotate-sections script.)

This plugin lets you record code coverage per unit test, and then
annotate your Python source code with which unit tests are running
which lines of code. It's a useful way to figure out which nose tests
are exercising what parts of your program.

See http://ivory.idyll.org/blog/feb-07/figleaf-goodness.html for some
detailed examples.

outputsave -- save your stdout into files

This plugin records the stdout from each test into a separate file,
with a prefix indicating whether or not the test succeeded.

spec -- generate test description from test class/method names

spec lets you generate a "specification" similar to testdox . The ppec
plugin can generate simple documentation directly from class and
method names of test cases.


Reply to: