d3773cbfbe
* Load plugins only if they are required This reduce a lot starting time of Rally and will allows us to do online bash completition As well it cleans up project structure a lot, e.g. all plugins are loaded in single place + we don't have strange code in cliutils * Replace rally.ui.utils to not import mako and remove all code on module level * Make Rally DB lazy inited * Import plugins during test run ---- The best way to test changes in start up time is to compare "time rally version" e.g.: before this patch: $ time rally version 0.0.5 real 0m0.397s user 0m0.299s sys 0m0.089s after this patch: 0.0.5 real 0m0.281s user 0m0.200s sys 0m0.077s Change-Id: Ibec2e6da66a1304730e801de307df7a1da68d51f |
||
---|---|---|
.. | ||
ci | ||
functional | ||
hacking | ||
unit | ||
__init__.py | ||
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.