Fuel testing
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Cao Xuan Hoang 876bee7572 Remove vim header from source files 2 years ago
etc Update tox.ini to skip dtabase creation steps 3 years ago
fuel_health Remove vim header from source files 2 years ago
fuel_plugin Merge "Clean imports in code" 2 years ago
specs Merge "Bump version to 10.0" 3 years ago
.gitignore Extended run_tests.sh to run Python tests 4 years ago
.gitreview Update paths due to stackforge migration 3 years ago
LICENSE LICENCE added 4 years ago
MAINTAINERS Add new Maintainers 3 years ago
MANIFEST.in Ostf config refactoring 4 years ago
README.md Update README.md 3 years ago
ostf.service Update ostf service for CentOS7 3 years ago
pylintrc Added pylintrc. 5 years ago
requirements.txt Sync with global requirements 2 years ago
run_tests.sh Add possibility invoke run_tests with coverage 3 years ago
setup.cfg Bump version to 10.0 3 years ago
setup.py Move setup.py to pbr usage 3 years ago
test-requirements.txt Extended run_tests.sh to run Python tests 4 years ago
tox.ini Update tox.ini to skip dtabase creation steps 3 years ago


Fuel OSTF tests

After OpenStack installation via Fuel, it is very important to understand whether it was successful and if it is ready for work. Fuel-ostf provides a set of health checks to be run against from Fuel console check the proper operation of all system components in typical conditions.

Details of Fuel OSTF tests

Tests are included to Fuel, so they will be accessible as soon as you install Fuel on your lab. Fuel ostf architecture is quite simple, it consists of two main packages:

  • fuel_health which contains the test set itself and related modules
  • fuel_plugin which contains OSTF-adapter that forms necessary test list in context of cluster deployment options and transfers them to UI using REST_API

On the other hand, there is some information necessary for test execution itself. There are several modules that gather information and parse them into objects which will be used in the tests themselves. All information is gathered from Nailgun component.

Python REST API interface

Fuel-ostf module provides not only testing, but also RESTful interface, a means for interaction with the components.

In terms of REST, all types of OSTF entities are managed by three HTTP verbs: GET, POST and PUT.

The following basic URL is used to make requests to OSTF:


Currently, you can get information about testsets, tests and testruns via GET request on corresponding URLs for ostf_plugin.

To get information about testsets, make the following GET request on:


To get information about tests, make GET request on:


To get information about executed tests, make the following GET requests:

for the whole set of testruns:


for the particular testrun:


for the list of testruns executed on the particular cluster:


To start test execution, make the following POST request on this URL:


The body must consist of JSON data structure with testsets and the list of tests belonging to it that must be executed. It should also have metadata with the information about the cluster (the key with the “cluster_id” name is used to store the parameter’s value):

        "testset": "test_set_name",
        "tests": ["module.path.to.test.1", ..., "module.path.to.test.n"],
        "metadata": {"cluster_id": id}


{...}, # info for another testrun



If succeeded, OSTF adapter returns attributes of created testrun entities in JSON format. If you want to launch only one test, put its id into the list. To launch all tests, leave the list empty (by default). Example of the response:

    "status": "running",
    "testset": "sanity",
    "meta": null,
    "ended_at": "2014-12-12 15:31:54.528773",
    "started_at": "2014-12-12 15:31:41.481071",
    "cluster_id": 1,
    "id": 1,
    "tests": [.....info on tests.....]


You can also stop and restart testruns. To do that, make a PUT request on testruns. The request body must contain the list of the testruns and tests to be stopped or restarted. Example:

    "id": test_run_id,
    "status": ("stopped" | "restarted"),
    "tests": ["module.path.to.test.1", ..., "module.path.to.test.n"]


{...}, # info for another testrun




There are next test targets that can be run to validate the code.

tox -e pep8 - style guidelines enforcement
tox -e py27 - unit and integration testing