openstack/rally-openstack
Code Issues Proposed changes
c2f3d7e067
rally-openstack/tests
History
Andrey Kurilin c2f3d7e067 [Services] Introduce Identity Service 
This patch introduces identity service. It is first step of unifying usage of
identity service and it bases on keystone wrapper.

Changes:
 - New service Identity is added with two version implementation(
   KeystoneServiceV2 and KeystoneServiceV3)
 - KeystoneWrapper is deprecated. It's impelemention is replaced by
   identity service
 - To reduce number of imports of eystoneclient around rally code,
   `_get_domain_id` method of KeystoneServiceV3 raises rally specific
   exception for 404 instead of keystone native exception
 - To avoid code duplication, `create_user` implementation of
   KeystoneServiceV3 starts using `list_roles` and `add_role` of Identity
   service instead of direct calls to keystoneclient.
 - Port several keystone scenarios related to roles to use IdentityService

TODO for further patches:
- move code from rally.plugins.openstack.scenarios.keystone.utils to Identity
  service
- add more support for Keystone V3

Change-Id: I266885d28232b02079968145063d88c675d02f11
2016-11-08 14:54:23 +02:00
..
ci Add nova resources in ci/osresources 2016-11-03 21:38:51 -04:00
functional [Tests] Fix functional test_time_hook 2016-10-18 15:33:33 +03:00
hacking Merge "replace assertNotEqual(*,None) to assertIsNotNone" 2016-07-27 17:56:57 +00:00
unit [Services] Introduce Identity Service 2016-11-08 14:54:23 +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.