openstack
/
tempest
Code Issues Proposed changes

Cleanup tempest quickstart 

This commit cleans up some of the tempest quickstart to have a better
flow, use consistent terminology, and clean up some wording and
formatting.

Change-Id: I889cf6d4ba92adf3b8bf185265c5ce197009c998
This commit is contained in:
Matthew Treinish 2016-07-01 13:55:05 -04:00
parent 85c8e3e60d
commit ab77cbfb72
No known key found for this signature in database
GPG Key ID: FD12A0F214C9E177
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.rst
View File

@ -70,12 +70,12 @@ as it is simpler, and quicker to work with.
it's recommended that you copy or rename tempest.conf.sample to tempest.conf it's recommended that you copy or rename tempest.conf.sample to tempest.conf
and make those changes to that file in /etc/tempest and make those changes to that file in /etc/tempest
#. Setup a local working Tempest dir. This is done by using the tempest init #. Setup a local Tempest workspace. This is done by using the tempest init
command:: command::
$ tempest init cloud-01 $ tempest init cloud-01
works the same as:: which also works the same as::
$ mkdir cloud-01 && cd cloud-01 && tempest init $ mkdir cloud-01 && cd cloud-01 && tempest init
@ -92,17 +92,18 @@ as it is simpler, and quicker to work with.
#. Once the configuration is done you're now ready to run Tempest. This can #. Once the configuration is done you're now ready to run Tempest. This can
be done using the :ref:`tempest_run` command. This can be done by either be done using the :ref:`tempest_run` command. This can be done by either
cd'ing into the tempest workspace directory and running:: running::
$ tempest run $ tempest run
Or use the ``--workspace`` argument to run in the workspace you created from the Tempest workspace directory. Or you can use the ``--workspace``
regarless of your current working directory. For example:: argument to run in the workspace you created regarless of your current
working directory. For example::
$ tempest run --workspace cloud-01 $ tempest run --workspace cloud-01
There is also the option to use testr directly, or any `testr`_ based test There is also the option to use testr directly, or any `testr`_ based test
runner, like `ostestr`_. For example, from the working dir running:: runner, like `ostestr`_. For example, from the workspace dir run::
$ ostestr --regex '(?!.*\[.*\bslow\b.*\])(^tempest\.(api|scenario))' $ ostestr --regex '(?!.*\[.*\bslow\b.*\])(^tempest\.(api|scenario))'