Tzanetos Balitsaris b439b4d127 Modify rally commands deployment, task, and verify
Small modifications to the rally commands 'deployment', 'task', and
'verify'.
In deployment, rename the subcommand endpoint to show, and remove
the pprint and json output options in subcommand config in favor of
pretty-printed json output only.
In task, perform the same in subcommand results as in config.
In verify, perform the same in subcommand results as in config.

Change-Id: I9686abf5088782e68111638da10be72c0e1135fa
2014-10-29 01:41:55 +02:00
..
2014-10-07 13:50:40 +00:00
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.