openstack/rally
Code Issues Proposed changes
5d9336fe29
rally/tests
History
Dmitrii Shcherbakov de4ea09398 Task context: implement comparison operators 
__cmp__ is no longer used in python3

Other operators need to be defined instead.

https://docs.python.org/3/whatsnew/3.0.html#ordering-comparisons
"The cmp() function should be treated as gone, and the __cmp__() special
method is no longer supported. Use __lt__() for sorting, __eq__() with
__hash__(), and other rich comparisons as needed. (If you really need
the cmp() functionality, you could use the expression (a > b) - (a < b)
as the equivalent for cmp(a, b).)"

https://www.python.org/dev/peps/pep-0207/

This change does it based on get_order and class meta properties.

Downstream projects that rely on context comparison (such as
rally-openstack) will benefit from this change.

Change-Id: I4991acccefd4754e209feafd5e24d03c76c283f8
Depends-On: I42db6045ae88c34d3576beb737bb7e955c5f2132
Needed-By: I6bb31fe1d3f79a8fd4707a5576204dee69a3f307
Partial-Bug: #1819274
2019-03-17 03:15:08 +03:00
..
ci [ci] Add job to run functional tests over py3 env 2019-02-04 18:01:13 +00:00
functional Fix test_time_hook functional test 2019-03-17 03:06:23 +03:00
hacking [cfg] Introduce rally.common.cfg 2018-02-12 15:49:26 +02:00
samples [task] Move TaskConfig to separate module 2018-08-16 17:04:03 +03:00
unit Task context: implement comparison operators 2019-03-17 03:15:08 +03: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.