openstack/rally-openstack

History

Cédric Savignan d6f8c33baf Modify Bgpvpn scenarios to test true bgpvpn Currently the bgpvpn scenarios test only a record in the database when a bgpvpn is created and associated with a network or a router. To test a true bgpvpn and not only a record in the neutron database a active port need to be created in the network associated to the bgpvpn. This change add a server which belong to a network in the context of all the bgpvpn scenarios concerned. If a bgpvpn driver is used on the openstack, a true bgpvpn is created. Change-Id: I64fb6bacf7866332ea55b3c5792bb23db366decd		2017-12-14 17:42:52 +01:00
..
check_samples	[ci] Split legacy-rally-dsvm-cli job	2017-12-01 14:35:35 +02:00
ci	Fix JSON generation when scenario has hooks	2017-12-01 14:22:28 +00:00
functional	[ci] Split legacy-rally-dsvm-cli job	2017-12-01 14:35:35 +02:00
hacking	Allow to specify resource name pattern via rally.conf	2017-10-09 13:15:23 +00:00
unit	Modify Bgpvpn scenarios to test true bgpvpn	2017-12-14 17:42:52 +01: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.