d87c97d01b
This patch marks v1 as deprecated. It'll be removed in the next cycle and we won't be fixing things for it anymore. This change should be reflected in the client library as well. In this patch, devstack has been switched to use v2 directly, which is the current developed/maintained version. APIImpact Change-Id: I2f32828835b3329b37bf7bac04024c46c161054a |
||
---|---|---|
.. | ||
wsgi | ||
__init__.py | ||
README.rst |
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