rally/tests
2014-11-28 21:57:28 +00:00
..
ci Add benchmark overview page to html report 2014-11-27 19:47:32 +02:00
functional rally info: smart substitutions in the non-ambiguous case 2014-11-28 13:37:36 +00:00
hacking TEMPEST: refactor error handling while installation 2014-11-24 12:23:37 +02:00
unit Merge "Add scenarios for security group" 2014-11-28 21:57:28 +00:00
__init__.py Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
README.rst Reorganize test module structure 2014-10-07 13:50:40 +00:00

Testing

Please, don't hesitate to write tests ;)

Unit tests

Files: /tests/unit/*

The goal of unit tests is to ensure that internal parts of the code work properly. All internal methods should be fully covered by unit tests with a reasonable mocks usage.

About Rally unit tests:

  • All unit tests are located inside /tests/unit/*
  • Tests are written on top of: testtools, fixtures and mock libs
  • Tox is used to run unit tests

To run unit tests locally:

$ pip install tox
$ tox

To run py26, py27 or pep8 only:

$ tox -e <name>

#NOTE: <name> is one of py26, py27 or pep8

To get test coverage:

$ tox -e cover

#NOTE: Results will be in /cover/index.html

To generate docs:

$ tox -e docs

#NOTE: Documentation will be in doc/source/_build/html/index.html

Functional tests

Files: /tests/functional/*

The goal of functional tests is to check that everything works well together. Fuctional tests use Rally API only and check responses without touching internal parts.

To run functional tests locally:

$ source openrc
$ rally deployment create --from-env --name testing
$ tox -e cli

#NOTE: openrc file with OpenStack admin credentials

Rally CI scripts

Files: /tests/ci/*

This directory contains scripts and files related to the Rally CI system.

Rally Style Commandments

File: /tests/hacking/checks.py

This module contains Rally specific hacking rules for checking commandments.