openinfra/interop
Code Issues Proposed changes

Updated docs with fixes and additional info

Browse Source 
Fixed the command to load the list of tests. Removed trailing
whitespace. Added more information about running tests and
addressed flagged failures.

Change-Id: Ifb8590f1da931f07cf6ffba1082c51cfac07143b
This commit is contained in:
Chris Hoge 2015-04-24 09:51:00 -07:00
parent ad6c04828a
commit 7117b237fa
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
2015.04/procedure.rst
View File

@ -58,17 +58,25 @@ or CentOS 7 have been verified) with administrator privileges.
directory: directory:
``cd .tempest`` ``cd .tempest``
``./run_tempest -C <your_tempest.conf> -- --load-tests 2015.04.required.txt`` ``./run_tempest -C <your_tempest.conf> -- --load-list 2015.04.required.txt``
* Review the test results, and when you're satisfied, send them to * Review the test results, and when you're satisfied, send them to
chris@openstack.org. The results are stored in a json file in the directory chris@openstack.org. The results are stored in a json file in the directory
``.tempest/.testrepository`` ``.tempest/.testrepository``
* Every effort should be made to pass all of the required tests, but you
will want to compare any lists of failed tests to the list of flagged tests.
https://github.com/openstack/defcore/blob/master/2015.03/2015.04.required.txt
Known Issues and Recommendations Known Issues and Recommendations
-------------------------------- --------------------------------
Currently after failures modes Tempest does not clean up test resources. We Currently after failures modes Tempest does not clean up test resources. We
strongly recommend that you run Tempest against a test OpenStack cloud strongly recommend that you run Tempest against a test OpenStack cloud
rather than a production cloud. Successful tests against test deployments that rather than a production cloud. Successful tests against test deployments that
are functionally equivalent to production clouds is acceptable for current are functionally equivalent to production clouds is acceptable for current
capabilities assessment. capabilities assessment.
You may find it useful to run Swift tests as a seperate run, using the
``accounts.yaml`` framework to specify users with Swift-specific roles.