Release 1.31.0

- capture exceptions in start_fixture as test errors

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

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 <fixtures>` 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
 ------
 

gabbi/__init__.py

@@ -12,4 +12,4 @@
 # under the License.
 """See gabbi.driver and gabbbi.case."""
 
-__version__ = '1.30.2'
+__version__ = '1.31.0'