openstack/tempest
Code Issues Proposed changes

Fix warnings from build_sphinx

Browse Source 
This commit fixes a couple of issues with build_sphinx in the tempest
docs.

Change-Id: Id8572455616e9be94a8c5794328eb9c1791db5b3
This commit is contained in:
Matthew Treinish 2014-06-04 11:43:10 -04:00
parent 6654c35ccd
commit 077a563bb2
2 changed files with 2 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -7,7 +7,7 @@ Scenarios, and other specific tests useful in validating an OpenStack
deployment. deployment.
Design Principles Design Principles
---------- -----------------
Tempest Design Principles that we strive to live by. Tempest Design Principles that we strive to live by.
- Tempest should be able to run against any OpenStack cloud, be it a - Tempest should be able to run against any OpenStack cloud, be it a
@ -127,6 +127,6 @@ currently only run with Python 2.7, so there are no guarantees about the state
of tempest when running with Python 2.6. Additionally, to enable testr to work of tempest when running with Python 2.6. Additionally, to enable testr to work
with tempest using python 2.6 the discover module from the unittest-ext with tempest using python 2.6 the discover module from the unittest-ext
project has to be patched to switch the unittest.TestSuite to use project has to be patched to switch the unittest.TestSuite to use
unittest2.TestSuite instead. See:: unittest2.TestSuite instead. See:
https://code.google.com/p/unittest-ext/issues/detail?id=79 https://code.google.com/p/unittest-ext/issues/detail?id=79

8
doc/source/index.rst
View File

@ -33,14 +33,6 @@ where your test contributions should go.
field_guide/thirdparty field_guide/thirdparty
field_guide/unit_tests field_guide/unit_tests
------------------
API and test cases
------------------
.. toctree::
:maxdepth: 1
api/modules
================== ==================
Indices and tables Indices and tables
================== ==================