zaqar/tests/functional
Sphoorti Joglekar 6253626829 Replace misleading max_message_size option name
The max_message_size option name is misleading. The option
determines max size of message post body. Replacing the
option name to max_messages_post_size.

Change-Id: Ie01cee026e7ebf530cdb2709e2c17d030ad95480
Closes-Bug: #1357397
2014-09-23 02:15:36 +05:30
..
wsgi Replace misleading max_message_size option name 2014-09-23 02:15:36 +05:30
__init__.py Pull actual tests out of marconi/tests 2013-09-06 10:56:41 +02:00
README.rst Rename Marconi to Zaqar 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