From ddb489cfe512eb135ba3a3174508431973129375 Mon Sep 17 00:00:00 2001
From: nayna-patel <nayna.patel@hp.com>
Date: Tue, 13 Nov 2012 22:06:45 +0000
Subject: [PATCH] fix for Bug1078481

Change-Id: I9b730abae07cf52b0ff4fd7b74e91cc4948630f5
---
 README.rst | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/README.rst b/README.rst
index 0ea5229042..04a4b3e765 100644
--- a/README.rst
+++ b/README.rst
@@ -35,13 +35,18 @@ and reference data to be used in testing.
 
     In addition, the ``<devstack-repo>/tools/configure_tempest.sh`` script can
     also be used to generate a tempest.conf based on your devstack's rc files.
+    TEMPEST_DIR variable points to location /opt/stack/temptest. Update this
+    variable if the location is different..
 
 Tempest is not tied to any single test runner, but Nose been the most commonly
 used tool. After setting up your configuration file, you can execute
 the set of Tempest tests by using ``nosetests`` ::
-
     $> nosetests tempest
 
+To run one single test  ::
+    $> nosetests -sv tempest.tests.compute.servers.test_server_actions.py:
+       ServerActionsTestJSON.test_rebuild_nonexistent_server
+
 Configuration
 -------------