zaqar/tests/functional
Shaifali Agrawal c3a5718775 Remove QueueController from data to control plane
To separate data and control plane of storage layer;
Moving queue_controller from data to controll plane.
Trying to shift the QueueController object in Control plane.
For this new MessageQueueHandler class is also added inside storage/x/messages.py
And the newly added handler is added to the entry point.

Implements: blueprint split-data-and-control-plane
Co-Author: Flavio Percoco<flavio@redhat.com>

Change-Id: I8a167d6ed8e54c98b077b9ea56e68b4e8d5b0291
2015-04-02 19:22:38 +02:00
..
2014-08-04 10:36:50 +02:00

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)

  1. Setup a Zaqar server. Refer to the Zaqar README on how to run Zaqar locally, or simply use an existing server.

  2. Change $ZAQAR_TESTS_CONFIGS_DIR/functional-tests.conf and set run_tests to True.

  3. Run tests. :

    $ tox
  4. Filter tests. :

    $ tox -- --tests tests.functional.wsgi.v1.test_messages
  5. Run tests for specific environments. :

    $ tox -epy27,pep8

Running the Functional Tests (Without Tox)

  1. Setup a Zaqar server. Refer to the Zaqar README on how to run Zaqar locally, or simply use an existing server.

  2. Install functional tests dependencies. :

    pip install -r requirements.txt
    pip install -r test-requirements.txt
  3. cd to the tests/etc directory

  4. If leaving keystone auth enabled, update functional-tests.conf with a valid set of credentials.

  5. Now, to run the system tests, simply use the nosetests commands, e.g.:

    Run all test suites: :

    nosetests -v

Adding New Tests

  1. Add test case to an appropriate test case file: :

    queue/test_queue.py
    messages/test_messages.py
    claim/test_claims.py