From fb9a001db765f113f92abbbde729cdc7e27fa2d4 Mon Sep 17 00:00:00 2001 From: Chris Dent Date: Tue, 17 Jan 2017 15:22:28 +0000 Subject: [PATCH] Release 1.31.0 - capture exceptions in start_fixture as test errors --- docs/source/fixtures.rst | 6 ++++++ docs/source/release.rst | 8 ++++++++ gabbi/__init__.py | 2 +- 3 files changed, 15 insertions(+), 1 deletion(-) diff --git a/docs/source/fixtures.rst b/docs/source/fixtures.rst index 630b168..e12d156 100644 --- a/docs/source/fixtures.rst +++ b/docs/source/fixtures.rst @@ -38,6 +38,12 @@ about the exception will be stored on the fixture so that the the fixture should clean up. The exception information can be found on ``exc_type``, ``exc_value`` and ``traceback`` method attributes. +If an exception is raised when a fixture is started (in +``start_fixture``) the first test in the suite using the fixture +will be marked with an error using the traceback from the exception +and all the tests in the suite will be skipped. This ensures that +fixture failure is adequately captured and reported by test runners. + .. _inner-fixtures: Inner Fixtures diff --git a/docs/source/release.rst b/docs/source/release.rst index 623e241..1e9616d 100644 --- a/docs/source/release.rst +++ b/docs/source/release.rst @@ -5,6 +5,14 @@ These are informal release notes for gabbi since version 1.0.0, highlighting major features and changes. For more detail see the `commit logs`_ on GitHub. +1.31.0 +------ + +Effectively capture a failure in a :doc:`fixture ` and +report the traceback. Without this some test runners swallow the +error and discovering problems when developing fixtures can be quite +challenging. + 1.30.0 ------ diff --git a/gabbi/__init__.py b/gabbi/__init__.py index 49122f0..930c59c 100644 --- a/gabbi/__init__.py +++ b/gabbi/__init__.py @@ -12,4 +12,4 @@ # under the License. """See gabbi.driver and gabbbi.case.""" -__version__ = '1.30.2' +__version__ = '1.31.0'