parent
93712a3ce6
commit
94ce5b0a5a
56
CHANGELOG
56
CHANGELOG
|
@ -1,23 +1,10 @@
|
||||||
Changes between 1.3.0 and 1.3.1
|
Changes between 1.3.0 and 1.3.1
|
||||||
==================================================
|
==================================================
|
||||||
|
|
||||||
- fix issue96: make capturing more resilient against Control-C
|
New features
|
||||||
interruptions (involved somewhat substantial refactoring
|
++++++++++++++++++
|
||||||
to the underlying capturing functionality to avoid race
|
|
||||||
conditions).
|
|
||||||
|
|
||||||
- fix issue89 - allow py.test.mark decorators to be used on classes
|
- issue91: introduce new py.test.xfail(reason) helper
|
||||||
(class decorators were introduced with python2.6)
|
|
||||||
also allow to have multiple markers applied at class/module level
|
|
||||||
|
|
||||||
- fix chaining of conditional skipif/xfail decorators - so it works now
|
|
||||||
as expected to use multiple @py.test.mark.skipif(condition) decorators,
|
|
||||||
including specific reporting which of the conditions lead to skipping.
|
|
||||||
|
|
||||||
- fix issue95: late-import zlib so that it's not required
|
|
||||||
for general py.test startup.
|
|
||||||
|
|
||||||
- fix issue91: introduce new py.test.xfail(reason) helper
|
|
||||||
to imperatively mark a test as expected to fail. Can
|
to imperatively mark a test as expected to fail. Can
|
||||||
be used from within setup and test functions. This is
|
be used from within setup and test functions. This is
|
||||||
useful especially for parametrized tests when certain
|
useful especially for parametrized tests when certain
|
||||||
|
@ -25,8 +12,10 @@ Changes between 1.3.0 and 1.3.1
|
||||||
declarative approach with the @py.test.mark.xfail cannot
|
declarative approach with the @py.test.mark.xfail cannot
|
||||||
be used as it would mark all configurations as xfail.
|
be used as it would mark all configurations as xfail.
|
||||||
|
|
||||||
- fix issue94: make reporting more robust against bogus source code
|
- issue89: allow py.test.mark decorators to be used on classes
|
||||||
(and internally be more careful when presenting unexpected byte sequences)
|
(class decorators were introduced with python2.6) and
|
||||||
|
also allow to have multiple markers applied at class/module level
|
||||||
|
by specifying a list.
|
||||||
|
|
||||||
- improve and refine letter reporting in the progress bar:
|
- improve and refine letter reporting in the progress bar:
|
||||||
. pass
|
. pass
|
||||||
|
@ -40,12 +29,13 @@ Changes between 1.3.0 and 1.3.1
|
||||||
skipped tests in the junitxml output - which also fixes
|
skipped tests in the junitxml output - which also fixes
|
||||||
issue99.
|
issue99.
|
||||||
|
|
||||||
- make py.test.cmdline.main() return the exitstatus
|
- make py.test.cmdline.main() return the exitstatus instead of raising
|
||||||
instead of raising (which is still done by py.cmdline.pytest())
|
SystemExit and also allow it to be called multiple times. This of
|
||||||
and make it so that py.test.cmdline.main() can be called
|
course requires that your application and tests are properly teared
|
||||||
multiple times, at least as far as py.test's internal
|
down and don't have global state.
|
||||||
state is concerned - previously it would raise an exception
|
|
||||||
on the second time.
|
Fixes / Maintenance
|
||||||
|
++++++++++++++++++++++
|
||||||
|
|
||||||
- improve tracebacks presentation:
|
- improve tracebacks presentation:
|
||||||
- raises shows shorter more relevant tracebacks
|
- raises shows shorter more relevant tracebacks
|
||||||
|
@ -53,7 +43,23 @@ Changes between 1.3.0 and 1.3.1
|
||||||
- improve support for raises and other dynamically compiled code by
|
- improve support for raises and other dynamically compiled code by
|
||||||
manipulating python's linecache.cache instead of the previous
|
manipulating python's linecache.cache instead of the previous
|
||||||
rather hacky way of creating custom code objects. This makes
|
rather hacky way of creating custom code objects. This makes
|
||||||
it seemlessly work on Jython and PyPy at least.
|
it seemlessly work on Jython and PyPy where it previously didn't.
|
||||||
|
|
||||||
|
- fix issue96: make capturing more resilient against Control-C
|
||||||
|
interruptions (involved somewhat substantial refactoring
|
||||||
|
to the underlying capturing functionality to avoid race
|
||||||
|
conditions).
|
||||||
|
|
||||||
|
- fix chaining of conditional skipif/xfail decorators - so it works now
|
||||||
|
as expected to use multiple @py.test.mark.skipif(condition) decorators,
|
||||||
|
including specific reporting which of the conditions lead to skipping.
|
||||||
|
|
||||||
|
- fix issue95: late-import zlib so that it's not required
|
||||||
|
for general py.test startup.
|
||||||
|
|
||||||
|
- fix issue94: make reporting more robust against bogus source code
|
||||||
|
(and internally be more careful when presenting unexpected byte sequences)
|
||||||
|
|
||||||
|
|
||||||
Changes between 1.2.1 and 1.3.0
|
Changes between 1.2.1 and 1.3.0
|
||||||
==================================================
|
==================================================
|
||||||
|
|
Loading…
Reference in New Issue