jiuyuan
/
test_ok1
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix issue50 (add a reference to the already implemented -m) and improve release annoucnement and changelog.

This commit is contained in:
holger krekel 2011-11-12 15:10:12 +00:00
parent f7c1b9087a
commit 9d3e51af9f
2 changed files with 27 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CHANGELOG
View File

@ -7,10 +7,10 @@ Changes between 2.1.3 and XXX 2.2.0
allowing to avoid typos and maintain a well described set of markers allowing to avoid typos and maintain a well described set of markers
for your test suite. See exaples at http://pytest.org/latest/mark.html for your test suite. See exaples at http://pytest.org/latest/mark.html
and its links. and its links.
- introduce "-m marker" option to select tests based on markers - issue50: introduce "-m marker" option to select tests based on markers
(this is a stricter and more predictable version of '-k' in that (this is a stricter and more predictable version of '-k' in that "-m"
"-m" only matches complete markers and has more obvious rules only matches complete markers and has more obvious rules for and/or
for and/or semantics. semantics.
- new feature to help optimizing the speed of your tests: - new feature to help optimizing the speed of your tests:
--durations=N option for displaying N slowest test calls --durations=N option for displaying N slowest test calls
and setup/teardown methods. and setup/teardown methods.

32
doc/announce/release-2.2.0.txt
View File

@ -1,11 +1,22 @@
py.test 2.2.0: new test duration profiling and bug fixes py.test 2.2.0: improved test markers and duration profiling
=========================================================================== ===========================================================================
pytest-2.2.0 is a quite backward compatible release of the popular pytest-2.2.0 is a quite (*) backward compatible release of the popular
py.test testing tool. It introduces the new "--duration=N" option py.test testing tool. It includes the following new features:
showing the N slowest test execution or setup/teardown calls. The
release also contains a few fixes and some cleanup of pytest's own test * new "--duration=N" option showing the N slowest test execution
suite allowing it to run on a wider range of environments. or setup/teardown calls.
* new "-m markexpr" option for selecting tests according to their mark
* new ini-variable for registering test markers and a "--strict"
option that will error out if you are using unregistered markers
Usages of the improved marking mechanism is illustrated by a couple
of initial examples, see XXX
Besides there is the usual set of bug fixes along with a cleanup of
pytest's own test suite allowing it to run on a wider range of environments.
For general information, see extensive docs with examples here: For general information, see extensive docs with examples here:
@ -16,19 +27,22 @@ If you want to install or upgrade pytest you might just type::
pip install -U pytest # or pip install -U pytest # or
easy_install -U pytest easy_install -U pytest
incompatible change
------------------------------------ (*) incompatible changes:
* You need a new version of the pytest-xdist plugin (1.7) for distributing * You need a new version of the pytest-xdist plugin (1.7) for distributing
test runs. test runs.
* Also other plugins might need an upgrade if they implement * Other plugins might need an upgrade if they implement
the ``pytest_runtest_logreport`` hook which now is called unconditionally the ``pytest_runtest_logreport`` hook which now is called unconditionally
for the setup/teardown fixture phases of a test. You can just choose to for the setup/teardown fixture phases of a test. You can just choose to
ignore them by inserting "if rep.when != 'call': return". Note that ignore them by inserting "if rep.when != 'call': return". Note that
most code probably "just" works because the hook was already called most code probably "just" works because the hook was already called
for failing setup/teardown phases of a test. for failing setup/teardown phases of a test.
Thanks to Ronny Pfannschmidt, David Burns, Jeff Donner XXX for their
help and feedback on various issues.
best, best,
holger krekel holger krekel