These were always called in series. No point to maintain the separation.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: Ic100f380eea90115f0a44a82d1d28d5d216bed68
This is effectively os-testr but maintained.
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Change-Id: I97183318f715b03f31145fa3d0f00bb7bc8a0c82
This allows to run functional live tests without devstack.
And runs tests within the normal tox target without devstack
This increases test coverage because all backend are now tested.
Change-Id: If475b6d1f43a44540f276209a3651e7e790c2233
AODH_TEST_BACKEND and AODH_SERVICE_URL are required to run functional
test. But it is a burden to export those two environment variables for
default devstack environment, this patch sets AODH_TEST_BACKEND=mysql
and AODH_SERVICE_URL=http://127.0.0.1:8042 if they are not set.
Change-Id: I5e977595dbbb0a01981f9317135ef1eb56602d7e
This replaces the usage of our custom bash scripts by overtest to setup
the daemon we need (PostgreSQL, MySQL and MongoDB).
Change-Id: I65e0358229043660c81f16ea8c624542bab1d19a
This provides a way to run functional tests from the gate, initially
just a simple set of gabbi tests which exercise the API. Once this
has proven to be working we can add more.
The model here is a hybrid of what was started for ceilometer and
what was used in gnocchi with some adjustments to allow for some
local testing.
The tests produced by test_gabbi_live will only run if
AODH_SERVICE_URL is set to the alarming endpoint. A keystone auth
token is needed in AODH_SERVICE_TOKEN. post_test_hook.sh
makes this happen if we are in a devstack-gate environment.
Otherwise they must be set by the caller.
The expectation is that we'll stick more test in tests/functional as
we have time, energy and brains.
Note that the layout of the functional tests assumes that the tests
will skip (or not even generate tests) if a functional environment
is not in place, such as when the unit tests are run.
Change-Id: Ia40e9c6b956209ecd0086ca861a90ce0c92b7b10
This CR allows running "functional" tox job for different backends.
Short description about expected workflow:
1. Gate job run ceilometer/ceilometer/tests/functional/hooks/post_test_hook.py
with <backend> parameter.
2. This script run "tox -efunctional" command with defined variable
CEILOMETER_TEST_BACKEND
3. After in "run-functional-tests.sh" setup script for the backend
and testr are runned.
In this CR running testr with pretty_tox.sh script added because
it allows to use subunit-trace output which developed in tempest-lib
and improve useful of testr output.
Partially implements: blueprint ceilometer-functional-tests
Change-Id: Idb66aca0b46779516db2baec856df8223dbe5c13
Stephen Finucane