This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (pypi.python.org).
Help us improve Python packaging - Donate today!
Project Description
testr recipe
============

This allows you to easily add a testrepository script to your buildout
project. This really only means that the user doesn't have to have
testr on their path, and they can just use ./bin/test or simlar.

This works very similarly to zc.recipe.testrunner, and in fact borrows
most of its code from there.

A sample buildout configuration would be::

[buildout]
develop = .
parts = test

[test]
recipe = testr_recipe
script = test

which will have ./bin/test run using the .testr.conf in your root
dir.

These are the options you can use:

* script: define the name of the script to create, if not passed
then the name of the section will be used.
* working-directory: if somewhere other than the root of the project
should be used.
* environment: the name of a section containing pairs of values to
put in the environment for the test run, e.g.

::

[test]
recipe = testr_recipe
enironment = testenv

[testenv]
foo = bar
zap = zang

* initialization: a string containing python code to put in the test
script before testr is run.
* executable: the python executable to put in the #! of the script.
* defaults: a list of options to prepend sys.argv for testr.
These are specified as Python source for an expression yielding a list,
typically a list literal. One thing you can do with this is::

[buildout]
parts = test testr

[testr]
recipe = testr_recipe

[test]
recipe = testr_recipe
defaults = ["run"]

which will make ./bin/test run the tests, and allow you to use
./bin/testr to access all the features of testr.

Creating the .testr.conf automatically
--------------------------------------

Given that buildout knows most things about your project you can
have it create the .testr.conf for you.

[testr]
recipe = testr_recipe
test-packages = mypackage
interpreter = python

Future enhancments:

* Maybe automatically doing "testr init" when setting up the project, so that
./bin/test works straight away.
Release History

Release History

0.3

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
testr_recipe-0.3.tar.gz (4.0 kB) Copy SHA256 Checksum SHA256 Source Jul 29, 2010

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting