History

Victoria Martínez de la Cruz ddabc98a99 Drop pylint due to the huge amount of false positives Given that pylint is raising a lot of false positives and that we have alternative static code checkers, we decided to remove pylint from the tox envlist. This patch also fix some pylint true positives and cleans up the disabled pylint tests in the codebase. Change-Id: I6fb4b9b4c80af452796032736e39ef064b9bcd03 Closes-Bug: #1297994		2014-07-13 20:03:52 -03:00
..
wsgi	Drop pylint due to the huge amount of false positives	2014-07-13 20:03:52 -03:00
README.rst	Merge "Fix functional config file instructions"	2014-03-25 03:27:18 +00:00
__init__.py	Pull actual tests out of marconi/tests	2013-09-06 10:56:41 +02:00

README.rst

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 functional tests (With Tox)

Setup a Marconi server. Refer to the Marconi README on how to run Marconi locally, or simply use an existing server.
Change $MARCONI_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 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 requirements.txt
pip install -r test-requirements.txt

cd to the marconi/tests/functional directory
Copy tests/etc/functional-marconi.conf 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 system tests, simply use the nosetests commands, e.g.:
Run all test suites: :
```
nosetests --tests tests.functional -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