
Some recent failulres in OpenStack land made it clear that it was less clear than it should be the precautions that are required when running gabbi in a concurrent testing environment.
2.6 KiB
Loading and Running Tests
To run gabbi tests with a test harness they must be generated in some
fashion and then run. This is accomplished by a test loader. Initially
gabbi only supported those test harnesses that supported the
load_tests
protocol in UnitTest. It now possible to also
build and run tests with pytest with
some limitations described below.
Note
It is also possible to run gabbi tests from the command line. See
runner
.
Warning
If test are being run with a runner that supports concurrency (such
as testrepository
) it is critical that the test runner is
informed of how to group the tests into their respective suites. The
usual way to do this is to use a regular expression that groups based on
the name of the yaml files. For example, when using
testrepository
the .testr.conf
file needs an
entry similar to the following:
group_regex=gabbi.suitemaker.(test[^_]+_[^_]+)
UnitTest Style Loader
To run the tests with a load_tests
style loader a test
file containing a load_tests
method is required. That will
look a bit like:
example.py
For details on the arguments available when building tests see ~gabbi.driver.build_tests
.
Once the test loader has been created, it needs to be run. There are
many options. Which is appropriate depends very much on your
environment. Here are some examples using unittest
or
testtools
that require minimal knowledge to get
started.
By file:
python -m testtools.run -v test/test_loader.py
By module:
python -m testttols.run -v test.test_loader
python -m unittest -v test.test_loader
Using test discovery to locate all tests in a directory tree:
python -m testtools.run discover
python -m unittest discover test
See the source
distribution and the
tutorial repo for more advanced options, including using
testrepository
and subunit
.
pytest
Since pytest does not support the load_tests
system, a
different way of generating tests is required. A test file must be
created that calls ~gabbi.driver.py_test_generator
and yields the
generated tests. That will look a bit like this:
pytest-example.py
This can then be run with the usual pytest commands. For example:
py.test -svx pytest-example.py