testresources

News and announcements

0.2.4 released

Written for testresources by Robert Collins on 2010-02-26

CHANGES
~~~~~~~

* Relicenced to BSD / Apache2.0 with full agreement of contributors.

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

* Substantially improved documentation in README. (mbp)

* Rename TestResource to TestResourceManager leaving TestResource as an alias.
  Fixes bug #520769.

* Test sorting no longer performs N! work on tests that can never benefit from
  order optimisations (when resources are not shared an arbitrary order is
  sufficient). Partial fix for bug #522338.

* Test sorting now uses a heuristic on each partition to get a sort that is
  no worse than twice the optimal number of setup/teardown operations and is
  fast to calculate. Fixes bug #522338

Read more

0.2.3 released

Written for testresources by Robert Collins on 2010-01-24

* Distribute doc/*.py in the source tarball.

* New helper testresources.GenericResource which should remove the need for
 much boilerplate when using testresources with existing test fixtures.

* New public functions testresources.setUpResources and
  testresources.tearDownResources for folk that cannot easily use
  ResourcedTestCase. Fixes bug #504146.

0.2.2 released

Written for testresources by Robert Collins on 2010-01-05

Test suites create by testresources.TestLoad().loadTests* were not optimising correctly, this point release fixes that.

testresources 0.2.1 released

Written for testresources by Robert Collins on 2009-12-12

Changes in testtools uncovered a small bug in the testresources test suite - a setUp upcall was missing. This has been corrected in 0.2.1, with no other changes made.

testresources 0.2 released!

Written for testresources by Jonathan Lange on 2009-07-17

Robert and I are pleased to announce the first ever release of testresources.

testresources has been out and about for some time now, but it's never had a proper release. Today, this changes.

If you haven't looked at testresources in a while, you'll notice that the API has changed a fair bit, the documentation has got a lot better and that the whole thing is a lot more stable and a lot less flaky.

Particular thanks to James Henstridge, who's been part guinea pig, part rubber-gloved scientist over the last few months.

1 → 5 of 5 results First • Previous • Next • Last

Announcements