openstack/tempest
Code Issues Proposed changes

Fix typo in Test Removal Procedure doc

Browse Source 
This commit fixes some typos in the Tempest Test Removal Procedure
document. The document was introduced by just copying from the wiki page
to this repo[1]. So we didn't paying attention at that time.

[1] I5f2322a5de7b73252e0162165eeaec120ec94948

Change-Id: Ia3b4f255cc688ddd4007cf80753923cb18799b98
This commit is contained in:
Masayuki Igawa 2016-07-11 18:59:23 +09:00
parent d519cb7195
commit a8d3cae7c2
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/test-removal.rst
View File

@ -31,7 +31,7 @@ In the proposal etherpad we'll be looking for answers to 3 questions
#. The tests proposed for removal must have equiv. coverage in a different
project's test suite (whether this is another gating test project, or an in
tree funcitonal test suite) For API tests preferably the other project will
tree functional test suite). For API tests preferably the other project will
have a similar source of friction in place to prevent breaking api changes
so that we don't regress and let breaking api changes slip through the
gate.
@ -62,7 +62,7 @@ The Old Way using subunit2sql directly
SELECT * from tests where test_id like "%test_id%";
(where $test_id is the full test_id, but truncated to the class because of
setupclass or teardownclass failures)
setupClass or tearDownClass failures)
You can access the infra mysql subunit2sql db w/ read-only permissions with:
@ -113,7 +113,7 @@ during a qa meeting during the tempest discussion. Please put it on the agenda
well ahead of the scheduled meeting. Since the meeting time will be well known
ahead of time anyone who depends on the tests will have ample time beforehand
to outline any concerns on the before the meeting. To give ample time for
people to respond to removal proposals please add things to the agend by the
people to respond to removal proposals please add things to the agenda by the
Monday before the meeting.
The other option is to raise the removal on the openstack-dev mailing list.
@ -163,6 +163,6 @@ is:
anything that lives in tempest which doesn't test one of these projects can be
removed assuming there is equivalent testing elsewhere. Preferably using the
`tempest plugin mechanism`_
to mantain continuity after migrating the tests out of tempest
to maintain continuity after migrating the tests out of tempest.
.. _tempest plugin mechanism: http://docs.openstack.org/developer/tempest/plugin.html