History

Boris Pavlovic 01289aa081 Improve Rally Logging (part 2)

- Remove translations

  Nobody is using translations for Rally and I don't think that
  anybody is going to use it. Target auditory for Rally are
  developers/operators which usually know well english.
  For me this looks like waste of resources, performance
  degradation (cause we are calling _()), complexity
  (+1 thing that you need to know)

- Pass to log already formatted strings

  It's very bad because in case of wrong formatting, it
  doesn't fail instead just writes errors to the logs,
  as well information about trace is lost, so it's super
  hard to fix it

  Log wrapper doesn't allow to use LOG anymore for
  formatting strings

  All places are fixed

- Improve logging of exceptions

LOG.exception() already logs exception, which means it's bad idea to
pass str(e) to it. Instead we should provide clear description of what
happend. Improved few places to write warnings or exceptions in case
of different level of logs. In few places just use LOG.exception

- Part of log messages were improved and simplified

Depends-On: If23d874e8b73de12ba2b8c4e028a55543af6381b
Change-Id: Ibc1e1f4f554649d14b8fe4801557b83922ecefe3

2017-10-05 22:57:39 +00:00

check_samples

Simplify deployment config format

2017-08-22 16:26:17 +03:00

Improve Rally Logging (part 2)

2017-10-05 22:57:39 +00:00

functional

Merge "Fix the problem of switching hooks format"

2017-09-27 13:08:25 +00:00

hacking

Improve Rally Logging (part 1)

2017-09-26 13:07:48 -07:00

unit

Merge "Improve Rally Logging (part 1)"

2017-09-27 18:25:53 +00: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.