openstack/rally-openstack
Code Issues Proposed changes
e27e2d30cc
rally-openstack/tests
History
Chris St. Pierre e27e2d30cc Minor install script improvements 
* Install wget/curl in install_required_sw(), where all other required
  software is installed.
* Fix and standardize exit. install_rally.sh used three different ways
  to stop execution: abort(); die(); and err() + exit. die() has a
  strange usage pattern, and there are several places that use a
  two-argument die() which happily waits for stdin forever. In other
  cases we had unique and exciting hacks to get around die()'s
  strangeness. This fixes all of those, and makes everything either
  use abort() or die() (correctly).
* Fix inconsistent say()/echo usage. This eliminates the rarely-used
  say() function entirely.
* Quoted things that need quoted. Some other minor changes
  recommended by shellcheck.

Change-Id: I1a9d0b2ff5daba02998245d5c7e624f46bd2242a
2015-05-19 14:27:41 -05:00
..
ci Minor install script improvements 2015-05-19 14:27:41 -05:00
functional Merge "Data structs declared with constructor replaced with literal" 2015-04-15 02:35:30 +00:00
hacking Data structs declared with constructor replaced with literal 2015-04-14 10:49:17 -07:00
unit Add E126 pep8 rule 2015-05-14 12:20:30 +00: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.