From deca3163a2883d8391488b834bb84338e12e3554 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Mon, 24 Feb 2014 01:03:50 -0500 Subject: [PATCH] changes to unit tests an changed to "a" sqlite to SQLite text plural changed Change-Id: I76aa0ddcca02a1c2cbe2eceec5469d4d57bf9f89 --- sources/cinder/unit_tests.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sources/cinder/unit_tests.xml b/sources/cinder/unit_tests.xml index 8da4dff7..1f1ec210 100644 --- a/sources/cinder/unit_tests.xml +++ b/sources/cinder/unit_tests.xml @@ -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:: Database -------- -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