History

Roman Vasilets 35c149c1a2 Refactor osclients

Now keystoneclient are separeted into 2 parts: working with resources
and authorization part. Secand part was moved into keystoneauth1 repo.

That patch is intended to drop depraceted usage of keystoneclient for
authorization in favor of keystoneauth1. Furthermore, in the next patch
we are going to use keystoneauth1 session for initialization of clients
where its possible.

Also :
  * Remove deprecated register decorator from osclient
  * Use _get_endpoint() in proper places
  * Refactor create_client in Keystone
  * Refactor unit tests in test_osclients

Change-Id: If67dffcd27f9bc3e7484d02eac62035c82415c3a

2016-07-25 12:49:45 +03:00

[requirements] Add helper for managing requirements

2016-07-20 17:58:55 +03:00

functional

Remove white space between print and ()

2016-07-05 16:38:05 +08:00

hacking

[requirements] Add helper for managing requirements

2016-07-20 17:58:55 +03:00

unit

Refactor osclients

2016-07-25 12:49:45 +03:00

__init__.py

Move tests to root dirrectory and fix tox

2013-08-28 19:08:07 +04:00

README.rst

[Requirements] Remove `fixtures' package

2016-06-06 15:38:44 +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 py26, py27 or pep8 only:

$ tox -e <name>

#NOTE: <name> is one of py26, py27 or pep8

To run py26, py27 against mysql or psql

$ export RALLY_UNITTEST_DB_URL="mysql://user:secret@localhost/rally" $ tox -epy27

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.