This commit switches to use stestr command to run unit tests directly.
Recently, the latest ostestr command uses stestr instead of testr.
However, we should use stestr directly because it's simple and straight
forward. There is no reason to use ostestr for unit tests anymore.
We still have the other ostestr/testr usage such as tempest run command
and documentations. So, that will be changed with following patches.
Change-Id: Iff4abef50178bdc83b868eed4a906e22d790762b
This commit introduces flake8-import-order to check import orders
automatically. We shouldn't do it manually.
Depends-On: Ia2140f5566ce169b076ffa5c9ebfbdbfc41e5bed
Change-Id: Iff75ebec42b295870edd1c04001adfb17460a682
The recent commit I45d73891f3c0829a2378a032dfc02e5ac0ee34b7
deduplicated the base test class methods from the tempest.lib
reintegration. However the surviving base class was put in the wrong
namespace. The base class is just that a base to build the individual
test subclass off of. It's very confusing for that to not live in the
base tests namespace. While the code in lib is supposed to be self
contained there isn't a reason to do that here for the unit tests,
especially because in this case the import heiarchy becomes more
confusing with the base living in a submodule. This commit moves the
base class to the base tempest.tests namespace where it really
belongs.
Change-Id: I079eeb1135eed3254e5e9dbebac8a52b979303c7
Those 2 files were identical. We should use `tempest.tests.lib.base`
now that we are commited to tempest.lib.
Change-Id: I45d73891f3c0829a2378a032dfc02e5ac0ee34b7
This commit fixes the last remaining issues in the tempest unit tests.
There were several failures for a couple of different issues previously
but after this running the tempest unit tests will pass on python 3.4.
Change-Id: Icf9090df83f8266a4683c88995c547e3c1bff523
We test whether or not testr fails to list all the tests, however
we're not being very nice about reporting when it fails (especially
not what caused the failure), and throw a cryptic 0 != 3 mismatch
error.
This should help make it easy to find syntax issues in the future.
Change-Id: I0d4b5b2a280813d54b0c2712a504e472370bd196
This commit adds onto the existing unit test which simply runs
'testr list-tests' to run discovery on tempest. This is done to ensure
that from a bare tempest repo with the requirements all present we can
actually import and list all the tests. However, there wasn't a check
of the return code. Historically this has been an issue with discovery
failing so adding a check to enforce it moving forward should prevent
it from slipping back in. Part of this is to also fix the test so that
it runs discovery on the correct test suite.
In order to make the unit test pass a config dependency in the
scenario test test_basic_server_ops during the testscenarios call in
load_tests had to be removed. Instead if there is a configuration
error raised while running load tests on this module instead of
failing it will just return the base test class. This is fine
because the test itself will fail on the same configuration
dependencies that load_tests is, however it won't happen silently
during discovery anymore.
Change-Id: Ie74c020de7c9c27adc4ff68dddbae5d4481d1224
We don't need to have the vim headers in each source files. We can set
it in our vimrc file instead. Also if set incorrectly, gate (pep8 check)
will catch the mistakes.
More discussions:
http://lists.openstack.org/pipermail/openstack-dev/2013-October/017353.html
Change-Id: I43703e2289212389c7841f44691ae7849ed1f505
Closes-Bug: #1229324
If there is an error in a test file it could potentially not get run
in the tox jobs used for gating. This commit adds a test which looks
for ImportFailures in the test list to ensure that all the test files
will get run in the gate.
Change-Id: Ia0a5831810d04f2201bd856039362b4a30f39319
Stephen Finucane