Files

Malini Kamalambal eedbc417ea Refactor System Tests

This patch,
1. Renames 'System Tests' to 'Functional Tests'.
2. Reduces LOC by using ddt.
3. Removes test dependencies & the numbering convention used earlier.
4. Re-organizes the test suite structure.

blueprint refactor-system-tests

Change-Id: Ife236abf867b678beb72ea3a26a06d895ed8ad4b

2013-08-29 14:08:04 -04:00

1.4 KiB

Raw Blame History

Marconi Functional Tests ====================

Marconi's functional tests treat Marconi 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 the Functional Tests ------------------------

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

Install functional tests dependencies. :

pip install -r functional-test-requirements.txt

cd to the marconi/tests/functional directory
Copy marconi/tests/etc/functional-tests.conf-sample to one of the following locations:
```
~/.marconi/functional-tests.conf
/etc/marconi/functional-tests.conf
```
Update the config file to point to the Marconi server you want to run the tests against
If leaving keystone auth enabled, update system-tests.conf with a valid set of credentials.
Now, to run the sytem tests, simply use the nosetests commands, from the marconi/tests/functional directory. 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

1.4 KiB Raw Blame History

Adding New Tests

1.4 KiB

Raw Blame History