Change [1] restored .testr.conf since it was needed for the manila
coverage job.
Modify script used by the coverage job to invoke stestr rather than
setup.py with testr so that this job no longer requires .testr.conf
so remove the dotfile and update .gitignore.
TrivialFix
[1] I451e383ed654d00a5a017cb28521c47566911f33
Change-Id: Ibf549220303395744380f79993fbfcf04b2ed5b7
Co-Authored-By: Tom Barron <tpb@dyncloud.net>
.testr.conf was removed in favor of .stestr.conf in
change [1] but the coverage job still uses it.
Restore it alongside .stestr.conf until we convert
the coverage job to use stestr.
[1] I6bb369624c4a790242022e203e771a77ffe06cf5
Closes-Bug: #1723655
Change-Id: I451e383ed654d00a5a017cb28521c47566911f33
In this change [1] os_testr changed under the covers from using
testr to stestr, so that we now get the following warning:
ostestr.py:120:
UserWarning: No .stestr.conf file found in the CWD.
Please create one to to replace the .testr.conf. You can find a
script to do this in the stestr git repository.
So remove the .testr.conf and add .stestr.conf which was
generated using a utility script as documented here [2].
[1] Id7cb2a39a8308f1413608dcf19273a1d7f33592e
[2] https://media.readthedocs.org/pdf/stestr/stable/stestr.pdf
TrivialFix
Change-Id: I6bb369624c4a790242022e203e771a77ffe06cf5
Switch to BaseTestCase as base class for all Manila test classes.
This BaseTestCase class automatically uses the following fixtures:
* fixtures.FakeLogger (only if needed)
* fixtures.NestedTempfile
* fixtures.TempHomeDir
so we don't have to explicit add them to our constructor.
Change-Id: I336d024f7008f5300e1882fa960a8e32439a9a70
Manila's test framework is pretty old and requires update.
Changes:
- usage of nose replaced with testr
- now all the tests are thread safe
- added new options for run_tests.sh, such as --concurrency, --debug, etc...
- new '--concurrency' option for run_tests.sh defaults to 1, examples:
./run_tests.sh # will run in 1 thread
./run_tests.sh --concurrency 2 # will run tests in 2 threads
- added tools/colorizer.py for colorizing output of testrun with run_tests.sh
- tests running with tox use as much threads as cores available by default
- examples of testrun with tox:
tox # will run test suites defined with 'envlist' in tox.ini, now it is pep8,py26,py27
tox -epy27 # amount of threads is equal to amount of cores
tox -epy27 -- --concurrency=2 # amount of threads is 2
tox -epy27 -- --concurrency=4 # amount of threads is 4
- Added 'Database' class to manila.test module, for more conveniant db testing
- updated policy file 'manila/tests/policy.json' to allow share-network actions
- removed nose-related requirements
- added new requirements for testrepository, subunit
With merge of this change all old installed virtual environments become
incompatible and should be removed with "rm -rf .tox .venv" before testrun.
Implements blueprint testr-with-unittests
Change-Id: I9579ecd538e29d478dbc12adc7dcc33fc668b397
lijunbo