openstack/rally
Code Issues Proposed changes
1c1b06f1a4
rally/tests
History
Boris Pavlovic 4719c5d8c7 [envs] Introduce Env Manager & Platforms (part 1) 
EnvManager is one of key Rally components,
It is actually replacment for Rally deployment component.
It manages and stores information about tested platforms.
Every Env has:
    - unique name and UUID
    - dates when it was created and updated
    - plugins spec and data
    - platforms names and data

Comparing to Rally deployment, env manager is way simpler and flat.
EnvManager manage Platforms (which are plugins)

However, even if it is simpler it allows to do way more flexible things
like manage multiple platforms in single env.

This patch:
- Introduce EnvManager
- Intorudce Platform plugin base
- Intorduce DB layer for Envs & Platforms
- Intrdouce 3 Exceptions:
-- ManagerException
---- ManagerInvalidSpec
---- ManagerInvalidState

Change-Id: Ide95c8b1e8e72293c009f4cd5e430e64eb1dd604
2018-01-11 23:49:31 -08:00
..
check_samples [ci] Split legacy-rally-dsvm-cli job 2017-12-01 14:35:35 +02:00
ci [ci] remove legacy things from install job 2017-12-20 14:08:29 +02:00
functional Make new report to support task file and remove old report 2017-12-18 13:46:09 +08:00
hacking Allow to specify resource name pattern via rally.conf 2017-10-09 13:15:23 +00:00
unit [envs] Introduce Env Manager & Platforms (part 1) 2018-01-11 23:49:31 -08:00
__init__.py Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
README.rst Add simple wrapper for pytest 2016-09-06 15:10:57 +03: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 and mock libs
  • Tox is used to run unit tests

To run unit tests locally:

$ pip install tox
$ tox

To run py27, py34, py35 or pep8 only:

$ tox -e <name>

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

To run py27/py34/py35 against mysql or psql

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

To run specific test of py27/py34/py35:

$ tox -e py27 -- tests.unit.test_osclients

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 directory 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 automatically generated file path and name if you need. You can use it to publish html reports, generated during tests. Reports root can be passed through 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.