openstack/training-guides
Code Issues Proposed changes

changes to unit tests

Browse Source 
an changed to "a"
sqlite to SQLite
text plural changed

Change-Id: I76aa0ddcca02a1c2cbe2eceec5469d4d57bf9f89
This commit is contained in:
Shilla Saebi 2014-02-24 01:03:50 -05:00
parent 46412ba49d
commit deca3163a2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
sources/cinder/unit_tests.xml
View File

@ -78,7 +78,7 @@ To run the `ToPrimitiveTestCase.test_dict` test method in
------------------------------------------
By default, when one or more unit test fails, all of the data sent to the
logger during the failed tests will appear on standard output, which typically
consists of many lines of texts. The logging output can make it difficult to
consists of many lines of text. The logging output can make it difficult to
identify which specific tests have failed, unless your terminal has a large
scrollback buffer or you have redirected output to a file.
You can suppress the logging output by calling ``run_tests.sh`` with the nose
@ -113,7 +113,7 @@ If you do not wish to use a virtualenv at all, use the flag::
<title>Database</title>
<para>
--------
Some of the unit tests make queries against an sqlite database [#f3]_. By
Some of the unit tests make queries against a SQLite database [#f3]_. By
default, the test database (``tests.sqlite``) is deleted and recreated each
time ``run_tests.sh`` is invoked (This is equivalent to using the
``-r, --recreate-db`` flag). To reduce testing time if a database already