openstack
/
tempest
Code Issues Proposed changes

Move tox execution to current docs section 

This commit moves the execution explanation of tempest run to the
current(non-legacy) docs section. In the original section of the tox
jobs are "Legacy run method" which discourages to use it. However, we
don't do it yet so far. So, this commit would make it clearer for using
the tox jobs as a tempest runner.

Change-Id: Iec6a956cba6949d0f30b0d0297ed26487e892125
This commit is contained in:
Masayuki Igawa 2019-06-05 19:04:59 +09:00
parent 71536f97b8
commit 80105b7c54
No known key found for this signature in database
GPG Key ID: 290F53EDC899BF89
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.rst
View File

@ -119,6 +119,17 @@ as it is simpler, and quicker to work with.
will run the same set of tests as the default gate jobs. Or you can
use `unittest`_ compatible test runners such as `testr`_, `pytest`_ etc.
Tox also contains several existing job configurations. For example::
$ tox -e full
which will run the same set of tests as the OpenStack gate. (it's exactly how
the gate invokes Tempest) Or::
$ tox -e smoke
to run the tests tagged as smoke.
.. _unittest: https://docs.python.org/3/library/unittest.html
.. _testr: https://testrepository.readthedocs.org/en/latest/MANUAL.html
.. _stestr: https://stestr.readthedocs.org/en/latest/MANUAL.html
@ -270,14 +281,3 @@ tests by using ``testr`` ::
To run one single test serially ::
$ testr run tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_reboot_non_existent_server
Tox also contains several existing job configurations. For example::
$ tox -e full
which will run the same set of tests as the OpenStack gate. (it's exactly how
the gate invokes Tempest) Or::
$ tox -e smoke
to run the tests tagged as smoke.