- update to 0.9.34:
* Added ability for ``testtools.TestCase`` instances to force a test to
fail, even if no assertions failed. (Thomi Richards)
* Added ``testtools.content.StacktraceContent``, a content object that
automatically creates a ``StackLinesContent`` object containing the current
stack trace. (Thomi Richards)
* ``AnyMatch`` is now exported properly in ``testtools.matchers``.
(Robert Collins, Rob Kennedy, github #44)
* Network tests now bind to 127.0.0.1 to avoid (even temporary) network
visible ports. (Benedikt Morbach, github #46)
- Revert back
- Totally disable testing to bootstrap ppc64. Actually the build conditional is
supposed to do just that.
OBS-URL: https://build.opensuse.org/request/show/213713
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=28
- Run testsuite
- Update to version 0.9.32:
+ Stacktrace filtering no longer hides unittest frames that are surrounded by
user frames. We will reenable this when we figure out a better algorithm for
retaining meaning. (Robert Collins, #1188420)
+ The compatibility code for skipped tests with unittest2 was broken.
(Robert Collins, #1190951)
+ Various documentation improvements (Clint Byrum, Xiao Hanyu).
- Changes from version 0.9.31:
+ ExpectedException now accepts a msg parameter for describing an error,
much the same as assertEquals etc. (Robert Collins)
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=20
- update to 0.9.30:
A new sort of TestResult, the StreamResult has been added, as a prototype for
a revised standard library test result API. Expect this API to change.
Although we will try to preserve compatibility for early adopters, it is
experimental and we might need to break it if it turns out to be unsuitable.
- update to 0.9.30:
A new sort of TestResult, the StreamResult has been added, as a prototype for
a revised standard library test result API. Expect this API to change.
Although we will try to preserve compatibility for early adopters, it is
experimental and we might need to break it if it turns out to be unsuitable.
- Update to version 0.9.24:
* testtools.run discover will now sort the tests it discovered. This is a
workaround for http://bugs.python.org/issue16709. Non-standard test suites
are preserved, and their sort_tests() method called (if they have such an
attribute). testtools.testsuite.sorted_tests(suite, True) can be used by
such suites to do a local sort.
* ThreadsafeForwardingResult now defines a stub progress method, which
fixes testr run of streams containing progress markers (by discarding the
progress data).
- Changes from version 0.9.23:
* run.TestToolsTestRunner now accepts the verbosity, buffer and failfast
arguments the upstream python TestProgram code wants to give it, making it
possible to support them in a compatible fashion. (Robert Collins)
* testtools.run now supports the -f or --failfast parameter.
Previously it was advertised in the help but ignored.
* AnyMatch added, a new matcher that matches when any item in a collection
matches the given matcher.
OBS-URL: https://build.opensuse.org/request/show/172922
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=14
* testtools.run discover will now sort the tests it discovered. This is a
workaround for http://bugs.python.org/issue16709. Non-standard test suites
are preserved, and their sort_tests() method called (if they have such an
attribute). testtools.testsuite.sorted_tests(suite, True) can be used by
such suites to do a local sort.
* ThreadsafeForwardingResult now defines a stub progress method, which
fixes testr run of streams containing progress markers (by discarding the
progress data).
- Changes from version 0.9.23:
* run.TestToolsTestRunner now accepts the verbosity, buffer and failfast
arguments the upstream python TestProgram code wants to give it, making it
possible to support them in a compatible fashion. (Robert Collins)
* testtools.run now supports the -f or --failfast parameter.
Previously it was advertised in the help but ignored.
* AnyMatch added, a new matcher that matches when any item in a collection
matches the given matcher.
* Spelling corrections to documentation.
* TestProgram now has a sane default for its testRunner argument.
* The test suite passes on Python 3 again.
- Changes from version 0.9.22:
* content_from_file and content_from_stream now accept seek_offset and
seek_whence parameters allowing them to be used to grab less than the full
stream, or to be used with StringIO streams.
* DirContains correctly exposed, after being accidentally hidden in the
- MatchesDict, match every key in a dictionary with a key in a
- ContainsDict, every key in a dictionary of matchers must be
- ContainedByDict, every key in a dictionary must be found in
testtools.matchers package and was thus completely broken. This release
* The testtools.matchers package has been split up. No change to the
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=9
* ``DirContains`` correctly exposed, after being accidentally hidden in the
great matcher re-organization of 0.9.17. (Jonathan Lange)
- 0.9.20
* New, powerful matchers that match items in a dictionary:
- ``MatchesDict``, match every key in a dictionary with a key in a
dictionary of matchers. For when the set of expected keys is equal to
the set of observed keys.
- ``ContainsDict``, every key in a dictionary of matchers must be
found in a dictionary, and the values for those keys must match. For
when the set of expected keys is a subset of the set of observed keys.
- ``ContainedByDict``, every key in a dictionary must be found in
a dictionary of matchers. For when the set of expected keys is a
superset of the set of observed keys.
The names are a little confusing, sorry. We're still trying to figure out
how to present the concept in the simplest way possible.
- 0.9.19
* Include the matcher tests in the release, allowing the tests to run and
pass from the release tarball. (Jonathan Lange)
* Fix cosmetic test failures in Python 3.3, introduced during release
0.9.17. (Jonathan Lange)
- 0.9.18
Due to an oversight, release 0.9.18 did not contain the new
``testtools.matchers`` package and was thus completely broken. This release
corrects that, returning us all to normality.
- 0.9.17
This release brings better discover support and Python3.x improvements.
There are still some test failures on Python3.3 but they are cosmetic - the
library is as usable there as on any other Python 3 release.
* The ``testtools.matchers`` package has been split up. No change to the
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=6
* ``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)
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=4
* 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)
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=3
- 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
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-testtools?expand=0&rev=2
