openstack/rally
Code Issues Proposed changes
654c63e328
rally/tests
History
Yaroslav Lobankov 178e98958a Small improvements for rally verify import 
1. Optional arguement "--set-name" was renamed into "--set" for
   consistency. See `rally verify start`.

2. The @envutils.with_default_deployment decorator was added to
   the import_results method.

3. When we import some results and don't specify set name for tests,
   in the verification table set name for these tests will be specified
   as None. So the default value of the "set_name" parameter was changed
   from None to "" to avoid this issue.

Change-Id: Icd6659f1a78c6a426c50c67cc31b7cd85f9fbd11
2015-10-02 17:22:25 +03:00
..
ci Merge "Moving commands for (re,un)instaling Tempest to "verify" category" 2015-09-25 09:53:10 +00:00
functional Run test_task_samples in separate sqlite db 2015-09-30 15:12:06 +03:00
hacking Move rally/objects -> rally/common/objects 2015-08-05 22:56:17 +03:00
unit Small improvements for rally verify import 2015-10-02 17:22:25 +03:00
__init__.py Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
README.rst Fix six typos and grammar inaccuracies in Rally Readme Files 2015-08-14 16:18:40 +05:30

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 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.