| 1 |
========= |
| 2 |
Changelog |
| 3 |
========= |
| 4 |
|
| 5 |
- :release:`2.0.2 <2024-03-29>` |
| 6 |
- :bug:`32` Fix dangling compatibility issues with pytest version 8.x. Thanks |
| 7 |
to Alex Gaynor for the patch! |
| 8 |
- :release:`2.0.1 <2023-05-22>` |
| 9 |
- :bug:`9` Don't try loading Pytest fixture functions as if they were test |
| 10 |
functions. Classifying this as a bug even though it's a moderately sized |
| 11 |
change in behavior; it's vanishingly unlikely anybody was relying on this |
| 12 |
somehow! Thanks to ``@cajopa`` for the report. |
| 13 |
- :release:`2.0.0 <2022-12-31>` |
| 14 |
- :bug:`- major` Prior to version 2, we failed to correctly support true Pytest |
| 15 |
setup/teardown methods (i.e. ``setup_method`` and ``teardown_method``) and |
| 16 |
these would not get copied to inner class scopes. This has been fixed. We |
| 17 |
still support old nose-style ``setup``/``teardown`` for now, despite them |
| 18 |
going away in Pytest 8. |
| 19 |
- :support:`-` Modernize codebase/project a bunch: |
| 20 |
|
| 21 |
- Dropped support for Python <3.6 (including 2.7) |
| 22 |
- Pytest support upgraded to support, **and require**, Pytest >=7. |
| 23 |
|
| 24 |
- This plugin never worked on Pytests 5 and 6 anyways, and supporting 5-7 |
| 25 |
appears to require a lot more effort than just 7. |
| 26 |
|
| 27 |
- Behavioral changes in Pytest internals have fixed a handful of sorta-bugs |
| 28 |
present in pytest-relaxed under Pytest versions 3 and 4: |
| 29 |
|
| 30 |
- The order of nested test display may change slightly, typically for the |
| 31 |
better; eg under older versions, tests defined on a class might have been |
| 32 |
displayed after subclasses/nested tests - now they're more likely to be |
| 33 |
listed first, which was the original intent. |
| 34 |
- These bugs sometimes enabled "state bleed", such as outer scopes |
| 35 |
appearing to grant inner ones attributes set at runtime (eg by the outer |
| 36 |
scope's ``setup``, even when the inner scope redefined ``setup``). |
| 37 |
|
| 38 |
- If you encounter odd bugs after upgrading, please take a close look at |
| 39 |
your code and make sure you weren't accidentally using such a |
| 40 |
"feature". One good way to test for this is to run the "newly failing" |
| 41 |
tests by themselves on the old dependencies -- they will likely also |
| 42 |
fail there. |
| 43 |
|
| 44 |
- :release:`1.1.5 <2019-06-14>` |
| 45 |
- :bug:`2` Fix compatibility with pytest versions 3.3 and above. |
| 46 |
- :release:`1.1.4 <2018-07-24>` |
| 47 |
- :release:`1.0.2 <2018-07-24>` |
| 48 |
- :support:`- backported` Add missing universal wheel indicator in setup |
| 49 |
metadata. |
| 50 |
- :release:`1.1.3 <2018-07-24>` |
| 51 |
- :release:`1.0.1 <2018-07-24>` |
| 52 |
- :bug:`-` Fix the ``@raises`` helper decorator so it actually raises an |
| 53 |
exception when the requested exception is not raised by the decorated |
| 54 |
function. That's definitely not a confusing sentence. |
| 55 |
- :release:`1.1.2 <2018-04-16>` |
| 56 |
- :bug:`-` Neglected to update setup metadata when setting up a tiny Read The |
| 57 |
Docs instance. Homepage link now fixed! |
| 58 |
- :release:`1.1.1 <2018-04-16>` |
| 59 |
- :bug:`-` Installation and other ``setup.py`` activities implicitly assumed |
| 60 |
native Unicode support due to naively opening ``README.rst``. ``setup.py`` now |
| 61 |
explicitly opens that file with a ``utf-8`` encoding argument. Thanks to |
| 62 |
Ondřej Súkup for catch & patch. |
| 63 |
- :bug:`-` Bypass ``pytestmark`` objects and attributes during our custom |
| 64 |
collection phase; we don't need to process them ourselves, pytest is already |
| 65 |
picking up the original top level copies, and having them percolate into |
| 66 |
nested classes was causing loud pytest collection-step warnings. |
| 67 |
- :release:`1.1.0 <2017-11-21>` |
| 68 |
- :feature:`-` Add support for collecting/displaying hybrid/legacy test suites |
| 69 |
-- specifically, by getting out of pytest's way on collection of |
| 70 |
``test_named_files`` and stripping test prefixes/suffixes when displaying |
| 71 |
tests in verbose mode. This makes it easier to take an existing test suite |
| 72 |
and slowly port it to 'relaxed' style. |
| 73 |
- :release:`1.0.0 <2017-11-06>` |
| 74 |
- :support:`-` Drop Python 2.6 and 3.3 support. |
| 75 |
- :feature:`-` Implement early drafts of Spec-like nested test display (which |
| 76 |
fires only when verbose output is enabled, unlike Spec which completely took |
| 77 |
over all output of nosetests.) |
| 78 |
- :support:`-` Revert internal tests to *not* eat our own dogfood; typical TDD |
| 79 |
lifecycles don't work very well when partly-implemented new features cause |
| 80 |
all of the older tests to fail as well! |
| 81 |
- :feature:`-` Create a ``@raises`` decorator which wraps ``pytest.raises`` |
| 82 |
(we're not sure why it's not natively offered as a decorator!) and thus ends |
| 83 |
up appearing very similar to Nose's API member of same name. |
| 84 |
- :feature:`-` Port ``@trap`` from Spec as it's currently a lot more natural to |
| 85 |
use than pytest's builtin capture fixtures. May back it out again later if |
| 86 |
we can make better sense of the latter / fit it into how our existing suites |
| 87 |
are organized. |
| 88 |
- :support:`-` Basic Travis and CodeCov support. |
| 89 |
- :bug:`- major` Various and sundry bugfixes, including "didn't skip |
| 90 |
underscore-named directories." |
| 91 |
- :release:`0.1.0 <2017-04-08>` |
| 92 |
- :feature:`-` Early draft functionality (test discovery only; zero display |
| 93 |
features.) This includes "releases" 0.0.1-0.0.4. |