Enable doc generation. Once Sphinx finally builds, it should start working

• Files Changed
• Browse Source

- Update to 0.9.15
  * ``PlaceHolder`` and ``ErrorHolder`` now support being given result
    details. (Robert Collins)
  * ``ErrorHolder`` is now just a function - all the logic is in
    ``PlaceHolder``. (Robert Collins)
  * ``TestResult`` and all other ``TestResult``-like objects in testtools
    distinguish between global tags and test-local tags, as per the subunit
    specification.  (Jonathan Lange)
  * This is the **last** release of testtools that supports Python 2.4 or 2.5.
    These releases are no longer supported by the Python community and do not
    receive security updates. If this affects you, you will need to either
    stay on this release or perform your own backports.
    (Jonathan Lange, Robert Collins)
  * ``ThreadsafeForwardingResult`` now forwards global tags as test-local
    tags, making reasoning about the correctness of the multiplexed stream
    simpler. This preserves the semantic value (what tags apply to a given
    test) while consuming less stream size (as no negative-tag statement is
    needed). (Robert Collins, Gary Poster, #986434)
  * API documentation corrections. (Raphaël Badin)
  * ``ConcurrentTestSuite`` now takes an optional ``wrap_result`` parameter
    that can be used to wrap the ``ThreadsafeForwardingResult``s created by
    the suite.  (Jonathan Lange)
  * ``Tagger`` added.  It's a new ``TestResult`` that tags all tests sent to
    it with a particular set of tags.  (Jonathan Lange)
  * ``testresultdecorator`` brought over from subunit.  (Jonathan Lange)
  * All ``TestResult`` wrappers now correctly forward ``current_tags`` from
    their wrapped results, meaning that ``current_tags`` can always be relied
    upon to return the currently active tags on a test result.
  * ``TestByTestResult``, a ``TestResult`` that calls a method once per test,
    added.  (Jonathan Lange)

• Files Changed
• Browse Source

- Update to 0.9.14:
  * Our sister project, `subunit <https://launchpad.net/subunit>`_, was using
    a private API that was deleted in the 0.9.13 release. This release
    restores that API in order to smooth out the upgrade path.
    If you don't use subunit, then this release won't matter very much to you.
- 0.9.13
  - Changes
    * ``MatchesAll`` now takes an ``first_only`` keyword argument that changes
      how mismatches are displayed. If you were previously passing matchers to
      ``MatchesAll`` with keyword arguments, then this change might affect
      your test results. (Jonathan Lange)
  - Improvements
    * Actually hide all of the testtools stack for assertion failures. The
      previous release promised clean stack, but now we actually provide it.
      (Jonathan Lange, #854769)
    * ``assertRaises`` now includes the ``repr`` of the callable that failed
      to raise properly. (Jonathan Lange, #881052)
    * Asynchronous tests no longer hang when run with trial.
      (Jonathan Lange, #926189)
    * ``Content`` objects now have an ``as_text`` method to convert their
      contents to Unicode text.  (Jonathan Lange)
    * Failed equality assertions now line up. (Jonathan Lange, #879339)
    * ``FullStackRunTest`` no longer aborts the test run if a test raises an
      error.  (Jonathan Lange)
    * ``MatchesAll`` and ``MatchesListwise`` both take a ``first_only``
      keyword argument.  If True, they will report only on the first mismatch
      they find, and not continue looking for other possible mismatches.
      (Jonathan Lange)
    * New helper, ``Nullary`` that turns callables with arguments into ones
      that don't take arguments.  (Jonathan Lange)

• Files Changed
• Browse Source

- Update to 0.9.12:
  - Changes:
    * ``AfterPreproccessing`` renamed to ``AfterPreprocessing``, which is a
      more correct spelling. Old name preserved for backwards compatibility,
      but is now deprecated.  Please stop using it.  (Jonathan Lange, #813460)
    * ``assertThat`` raises ``MismatchError`` instead of
      ``TestCase.failureException``.  ``MismatchError`` is a subclass of
      ``AssertionError``, so in most cases this change will not matter.
      However, if ``self.failureException`` has been set to a non-default
      value, then mismatches will become test errors rather than test
      failures.
    * ``gather_details`` takes two dicts, rather than two detailed objects.
      (Jonathan Lange, #801027)
    * ``MatchesRegex`` mismatch now says "<value> does not match /<regex>/"
      rather than "<regex> did not match <value>". The regular expression
      contains fewer backslashes too. (Jonathan Lange, #818079)
    * Tests that run with ``AsynchronousDeferredRunTest`` now have the
      ``reactor`` attribute set to the running reactor. (Jonathan Lange,
      #720749)
  - Improvements:
    * All public matchers are now in ``testtools.matchers.__all__``. (Jonathan
      Lange, #784859)
    * ``assertThat`` can actually display mismatches and matchers that contain
      extended unicode characters. (Jonathan Lange, Martin [gz], #804127)
    * ``assertThat`` output is much less verbose, displaying only what the
      mismatch tells us to display. Old-style verbose output can be had by
      passing ``verbose=True`` to assertThat. (Jonathan Lange, #675323,
      #593190)
    * ``assertThat`` accepts a message which will be used to annotate the
      matcher. This can be given as a third parameter or as a keyword

• Files Changed
• Browse Source

- Initial release

• Browse Source