44b5f310c5
Python 3 introduced a next() function to replace the next() method on iterator objects. Rather than calling the method on the iterator, the next() function is called with the iterable object as it's sole parameter, which calls the underlying __next__() method. The next() function was backported to Python 2.6 which allows us to use either the 2.x or 3.x way simultaneously. Change-Id: I945225b1b0c6c39842a77f4a136e9431b798229f Closes-Bug: #1403074 |
||
|---|---|---|
| .. | ||
| 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
$ toxTo run py26, py27 or pep8 only:
$ tox -e <name>
#NOTE: <name> is one of py26, py27 or pep8To get test coverage:
$ tox -e cover
#NOTE: Results will be in /cover/index.htmlTo generate docs:
$ tox -e docs
#NOTE: Documentation will be in doc/source/_build/html/index.htmlFunctional 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 credentialsRally 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.