5881bec6a6
This patch is proposed according to the Direction 10 of doc migration(https://etherpad.openstack.org/p/doc-migration-tracking). Change-Id: Ifdf9aa3a03d268ba13c2d7c2f15ec728b909c37d
27 lines
1.2 KiB
ReStructuredText
27 lines
1.2 KiB
ReStructuredText
Tacker Style Commandments
|
|
================================
|
|
|
|
- Step 1: Read the OpenStack Style Commandments
|
|
https://docs.openstack.org/hacking/latest
|
|
- Step 2: Read on
|
|
|
|
|
|
Running Tests
|
|
-------------
|
|
The testing system is based on a combination of tox and testr. The canonical
|
|
approach to running tests is to simply run the command `tox`. This will
|
|
create virtual environments, populate them with depenedencies and run all of
|
|
the tests that OpenStack CI systems run. Behind the scenes, tox is running
|
|
`testr run --parallel`, but is set up such that you can supply any additional
|
|
testr arguments that are needed to tox. For example, you can run:
|
|
`tox -- --analyze-isolation` to cause tox to tell testr to add
|
|
--analyze-isolation to its argument list.
|
|
|
|
It is also possible to run the tests inside of a virtual environment
|
|
you have created, or it is possible that you have all of the dependencies
|
|
installed locally already. In this case, you can interact with the testr
|
|
command directly. Running `testr run` will run the entire test suite. `testr
|
|
run --parallel` will run it in parallel (this is the default incantation tox
|
|
uses.) More information about testr can be found at:
|
|
https://wiki.openstack.org/wiki/Testr
|