Set the default OS_TEST_PATH in the stestr configuration file. Any
other test environment can overwrite this variable in the "setenv"
section.
Change-Id: I51564920cec916031aaebf8151b015a3d87e9471
Sometimes the test_connection_reconnect test will interact with
other tests causing a failure. Telling stestr to keep all tests
in a class together in the same process seems to fix this issue.
Change-Id: Ic20b08b7bae2f6b5b8dc3a7607c1e6bf7044b95c
When running tox -e functional, stestr was running the unit tests.
Changing .stestr.conf to use ${OS_TEST_PATH} seems to fix it. Two
functional tests were not passing when I made this change, so I
fixed those as well so this change wouldn't fail the gate.
Change-Id: I6c4a3ff7a50aca925dca1d7f9cfe83e99fedaa50
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I32db99af179412f46b02ced9eaf61049cbffcdb0
Rodolfo Alonso Hernandez