History

Andrey Kurilin fb8a67740b Fix validation of required services

Cinder team decided to remove Cinder V1 (which is ok since they already
have V3 API) but our logic of required_service validator was not ready
for such step.

This patch includes the next changes of the validaotr:

* Check for nova-network before initializing clients. This is a simple
  check which does not require initialized clients. Since the keystone
  token is fetched while initializing clients, it can be time wasting.
  Also, it is time to fail on this check.

* In case of NotFound error while direct search by service type, use the
  default one
  NOTE: actually, the default service type should be the same as  what
        we have in consts file...

Change-Id: I2018a9b9323cce05ee226fefdc3fe50c356aed9a

2019-02-19 19:27:10 +02:00

[ci] run osresources script from proper python binary

2018-12-17 00:44:08 +02:00

functional

Merge "[api_versions]Add api check into health check"

2018-09-13 09:53:15 +00:00

hacking

Fix fetching osprofiler trace-info

2018-11-06 16:18:04 +02:00

unit

Fix validation of required services

2019-02-19 19:27:10 +02: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.