zaqar/tests/functional
Flavio Percoco 401213ab4f Claim post requires a body
One of the claim's test scenario used to send `None` to the server. The
later failed to deserialize this body and the response returned 400.
This patch removes `None` from the test scenario since a body is
requires to created a claim to begin with.

Change-Id: If2c6acefc84fb2b7cc5b4a26e1784b74a1ae1e22
Closes-bug: #1383604
2014-11-17 13:02:41 +00:00
..
2014-11-17 13:02:41 +00: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