Testrepository

Testrepository 0.0.3

  1. Series trunk
  2. 0.0.3

Milestone information

Project:
Testrepository
Series:
trunk
Version:
0.0.3
Released:
 
Registrant:
Robert Collins
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon dist-testrepository-0.0.3.tar.gz (md5, sig) release tarball 37
last downloaded 19 weeks ago
Total downloads: 37

Release notes 

* ``testr failing`` now tracks all failures rather than just the most recent ones.

* ``testr run`` can run a test suite and automatically gather the results.

* ``test last`` no longer errors on new repositories.

Changelog 

View the full changelog

0.0.3
-----

IMPROVEMENTS
~~~~~~~~~~~~

* ``failing`` now correctly calls ``repository.get_failing`` and will this
  track all seen failures rather than just the latest observed failures.

* New argument type ``StringArgument`` for use when a supplied argument is just
  a string, rather than a typed argument.

* New subcommand 'failing' added.

* New subcommand ``run`` added which reads a .testr.conf file to figure out how
  to run tests with subunit output. It then runs them and pipes into testr
  load. This allows simpler integration and permits a programming interface so
  that tools like Tribunal/Eclipe etc can refresh tests in a testrepository.
  ``run`` also passes arguments and options down to the child process. ``run``
  can also supply test ids on the command, for test runners that want that.

* The command 'last' will no longer error on a new repository.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.