Testtools

~~~~~

Changes
-------

* Fixed our setup.py to use setup_requires to ensure the import dependencies
for testtools are present before setup.py runs (as setup.py imports testtools
to read out the version number). (Robert Collins)

* Support setUpClass skipping with self.skipException. Previously this worked
with unittest from 2.7 and above but was not supported by testtools - it was
a happy accident. Since we now hard depend on unittest2, we need to invert
our exception lookup priorities to support it. Regular skips done through
raise self.skipException will continue to work, since they were always caught
in our code - its because the suite type being used to implement setUpClass
has changed that an issue occurred.
(Robert Collins, 1393068)

~~~~~

Changes
-------

* Correctly express our unittest2 dependency: we don't work with old releases.
(Robert Collins)

~~~~~

Changes
-------

* Depends on unittest2 for discovery functionality and the ``TestProgram`` base
class. This brings in many fixes made to discovery where previously we were
only using the discovery package or the version in the release of Python
that the test execution was occurring on. (Robert Collins, 1271133)

* Fixed unit tests which were failing under pypy due to a change in the way
pypy formats tracebacks. (Thomi Richards)

* Fixed the testtools test suite to run correctly when run via ``unit2``
or ``testtools.run discover``.

* Make `testtools.content.text_content` error if anything other than text
is given as content. (Thomi Richards)

* We now publish wheels of testtools. (Robert Collins, issue84)

~~~~~

Improvements
------------

* Exceptions in a ``fixture.getDetails`` method will no longer mask errors
raised from the same fixture's ``setUp`` method.
(Robert Collins, 1368440)

~~~~~

Long overdue, we've adopted a backwards compatibility statement and recognized
that we have plenty of users depending on our behaviour - calling our version
1.0.0 is a recognition of that.

Improvements
------------

* Fix a long-standing bug where tearDown and cleanUps would not be called if the
test run was interrupted. This should fix leaking external resources from
interrupted tests.
(Robert Collins, 1364188)

* Fix a long-standing bug where calling sys.exit(0) from within a test would
cause the test suite to exit with 0, without reporting a failure of that
test. We still allow the test suite to be exited (since catching higher order
exceptions requires exceptional circumstances) but we now call a last-resort
handler on the TestCase, resulting in an error being reported for the test.
(Robert Collins, 1364188)

* Fix an issue where tests skipped with the ``skip``* family of decorators would
still have their ``setUp`` and ``tearDown`` functions called.
(Thomi Richards, https://github.com/testing-cabal/testtools/issues/86)

* We have adopted a formal backwards compatibility statement (see hacking.rst)
(Robert Collins)

~~~~~~

Brown paper bag release - 0.9.38 was broken for some users,
_jython_aware_splitext was not defined entirely compatibly.
(Robert Collins, https://github.com/testing-cabal/testtools/issues/100)