Update unit test debugging instructions for stestr

Updates our instructions for debugging unit tests to use the stestr way
of doing it since we normally run our unit tests using stestr.

Change-Id: If1f320b2e288ba69d3fdb324b9919d84f6dfdd4f
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2019-04-17 16:29:04 -05:00
parent 5921b36ceb
commit dbd4a100fe
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8

View File

@ -232,11 +232,11 @@ Then run the unit test with pdb enabled:
.. code-block:: bash
source .tox/py35/bin/activate
source .tox/py36/bin/activate
python -m testtools.run cinder.tests.unit.test_volume_utils
stestr run -n cinder.tests.unit.test_volume_utils
# Or to get a list of tests to run
python -m testtools.run discover -t ./ cinder/tests/unit --list | grep group > tests_to_run.txt
python -m testtools.run --load-list tests_to_run.txt
stestr list test_volume_utils > tests_to_run.txt
stestr run -n --load-list tests_to_run.txt