Clean up test requirements

remove os-testr and testrepository in favor of stestr,
and remove qpid-python (does not seem to be imported anywhere).

Also adjust docs to describe running tests with stestr instead of
testrepository.

Change-Id: I12088ea2bf2475963db58d6e8e83fd6abe6f9b3f

1 files changed, 13 insertions, 11 deletions

diff --git a/HACKING.rst b/HACKING.rst
index 9b0cadee5..618cfa309 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -24,22 +24,24 @@ infrastructure in OpenStack Heat, please read heat/tests/testing-overview.txt.
 
 Running tests
 -------------
-The testing system is based on a combination of tox and testr. The canonical
-approach to running tests is to simply run the command `tox`. This will
+The testing system is based on a combination of tox and stestr. The canonical
+approach to running tests is to simply run the command ``tox``. This will
 create virtual environments, populate them with dependencies and run all of
 the tests that OpenStack CI systems run. Behind the scenes, tox is running
-`testr run --parallel`, but is set up such that you can supply any additional
-testr arguments that are needed to tox. For example, you can run:
-`tox -- --analyze-isolation` to cause tox to tell testr to add
---analyze-isolation to its argument list.
+``stestr run``, but is set up such that you can supply any additional
+stestr arguments that are needed to tox. For example, you can run:
+``tox -- --analyze-isolation`` to cause tox to tell stestr to add
+``--analyze-isolation`` to its argument list.
 
 It is also possible to run the tests inside of a virtual environment
 you have created, or it is possible that you have all of the dependencies
-installed locally already. In this case, you can interact with the testr
-command directly. Running `testr run` will run the entire test suite. `testr
-run --parallel` will run it in parallel (this is the default incantation tox
-uses.) More information about testr can be found at:
-http://wiki.openstack.org/testr
+installed locally already. In this case, you can interact with the ``stestr``
+command directly. Running ``stestr run`` will run the entire test suite in
+as many threads as you have CPU cores (this is the default incantation tox
+uses), number of threads can be adjusted with ``--concurrency N`` argument.
+``testr run --serial`` will run tests in serial process.
+More information about stestr can be found at:
+http://stestr.readthedocs.io
 
 Note that unit tests use a database if available. See
 ``tools/test-setup.sh`` on how to set up the databases the same way as