This patch removes the sqlalchemy as a valid data driver. In order to make this work properly, we also need the data plane to be properly split into 2 completely independent pipelines. This patch, unfortunately, disables some of the sqlalchemy's tests for queues and pools. The reason is that, until these planes are correctly separated and pooling is enabled by default, we won't be able to properly run those tests. A follow-up patch, expected to land in kilo, will do this. DocImpact Implements blueprint: disable-sqlalchemy-as-pool Change-Id: I5ca73102241692b0e1b23b3eaaaf1938f0106dfa
Zaqar Functional Tests
Zaqar's functional tests treat Zaqar as a black box. In other words, the API calls attempt to simulate an actual user. Unlike unit tests, the functional tests do not use mockendpoints.
Running functional tests (With Tox)
Setup a Zaqar server. Refer to the Zaqar README on how to run Zaqar locally, or simply use an existing server.
Change $ZAQAR_TESTS_CONFIGS_DIR/functional-tests.conf and set run_tests to True.
Run tests. :
$ tox
Filter tests. :
$ tox -- --tests tests.functional.wsgi.v1.test_messages
Run tests for specific environments. :
$ tox -epy27,pep8
Running the Functional Tests (Without Tox)
Setup a Zaqar server. Refer to the Zaqar README on how to run Zaqar locally, or simply use an existing server.
Install functional tests dependencies. :
pip install -r requirements.txt pip install -r test-requirements.txt
cd to the tests/etc directory
If leaving keystone auth enabled, update functional-tests.conf with a valid set of credentials.
Now, to run the system tests, simply use the nosetests commands, e.g.:
Run all test suites: :
nosetests -v
Adding New Tests
Add test case to an appropriate test case file: :
queue/test_queue.py messages/test_messages.py claim/test_claims.py