0.11.0 (2022-02-12)

This is the first version of nose2 using sphinx-issues to credit contributors in the changelog.

Added

• Test classes now have their short description (first line of docstring) printed in verbose output
• The junitxml plugin now sets timestamp on each testcase node as an ISO-8601 timestamp. Thanks to deeplow for the contribution!

Changed

• Drop support for Python 3.5
• Python 3.10 is now officially supported. Python 3.11-dev will be supported on a best-effort basis. Thanks to hugovk and tirkarthi for their contributions!
• nose2 source code is now autoformatted with black and isort
• nose2 has switched its main development branch from master to main
• Releases are now published using build

Fixed

• Add support for test classes when running with the multiprocessing plugin. Thanks to ltfish for the initial contribution and stefanholek for the refinement to this change!
• Various documentation fixes

0.10.0 (2021-01-27)

Added

• Support for subtests!

Notes for plugin authors about subtest support:

• Subtest failures will produce a TestOutcomeEvent with outcome = "subtest"
• Subtest events can be failures, but they do not indicate success -- the containing test will send a success event if no subtests fail

Changed

• Drop support for Python 3.4
• Python 3.8 and 3.9 are now officially supported
• Improve helptext for the multiprocess plugin's -N option
• When run with reduced verbosity (e.g. with -q), nose2 will no longer print an empty line before test reports

Fixed

• The plugin registry will no longer contain duplicate plugins and or base event.Plugin instances
• Fix function test case implementation of id, __str__, and __repr__. This removes the injected transplant_class.<locals> from reporting output
• Doctest loading will now skip setup.py files in the project root
• Class methods decorated (e.g. with mock.patch) are no longer incorrectly picked up by the function loader

0.9.2 (2020-02-02)

Added

• Add --junit-xml-path to the junit plugin argument list

Fixed

• It is now possible to use the multiprocess and coverage plugins together, as long as all of the coverage config is put into the config file
• Minor changes to be compatible with newer pythons (3.8, 3.9)