Files

Pavel Boldin 7fd4973be5 Introduce command-dict and validator

Refactor `vm.utils._run_command_over_ssh' making it accept a dict to
specify command as either local script file, inline script or remote
script path. Both local and inline scripts require `interpreter' being
specified. Any of the above can be a list specifying e.g. environment
variables (for `interpreter') or command args.

Introduce `valid_command' validator that checks whether the specified
command dictionary is a valid one.

Change-Id: I3c495297251c87529b9adf1e769cfe277338f5fc
Implements: blueprint vm-workloads-framework

2015-06-08 18:13:24 +03:00

Merge "Improvement of cover script"

2015-05-27 12:53:20 +00:00

functional

Merge "Add functional test for --plugin-paths parameter"

2015-06-05 23:44:13 +00:00

hacking

Data structs declared with constructor replaced with literal

2015-04-14 10:49:17 -07:00

unit

Introduce command-dict and validator

2015-06-08 18:13:24 +03:00

__init__.py

Move tests to root dirrectory and fix tox

2013-08-28 19:08:07 +04:00

README.rst

Publishing functional tests reports

2015-02-10 06:49:46 +02:00

README.rst

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 run py26, py27 against mysql or psql

$ export RALLY_UNITTEST_DB_URL="mysql://user:secret@localhost/rally" $ tox -epy27

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 --fromenv --name testing
$ tox -e cli

#NOTE: openrc file with OpenStack admin credentials

Output of every Rally execution will be collected under some reports root in directiry structure like: reports_root/ClassName/MethodName_suffix.extension This functionality implemented in tests.functional.utils.Rally.__call__ method. Use 'gen_report_path' method of 'Rally' class to get automaticaly generated file path and name if you need. You can use it to publish html reports, generated during tests. Reports root can be passed throw environment variable 'REPORTS_ROOT'. Default is 'rally-cli-output-files'.

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.