openstack/rally-openstack
Code Issues Proposed changes
ea3672e1f7
rally-openstack/tests
History
Alexander Maretskiy ea3672e1f7 [Tests] Some fixes in SaharaInputDataSourcesTestCase 
There are some updates in
test_sahara_input_data_sources.SaharaInputDataSourcesTestCase

The main reason why this patch is submitted is that we have
some not mocked modules in this test class, so the result is
real calling of python clients and having a message in tests
output:

   "Could not find Sahara endpoint in catalog"

This message appears sometimes in tox output (due to side
effects of concurrent testing) but always appears while running
tests in single thread:

 .tox/py27/bin/python -m unittest discover tests/unit

Affected methods:

  * setUp()
    - removed unnecessary usage of objects.Endpoint
    - better context generation: each user now has different
      credentials, not same for all
    - removed unused code

  * test_setup_inputs_swift()
    - added missed mocks
    - added missed assertions

Change-Id: If611432bd23a55d39687bc383c3817f284887283
2016-03-28 16:02:17 +03:00
..
ci [CI] Check nova is available in deployment 2016-03-17 17:08:08 +03:00
functional Add Workload object 2015-12-04 13:58:02 +00:00
hacking Using 'dt' as alias for datetime imports 2016-02-22 20:04:34 +08:00
unit [Tests] Some fixes in SaharaInputDataSourcesTestCase 2016-03-28 16:02:17 +03:00
__init__.py Move tests to root dirrectory and fix tox 2013-08-28 19:08:07 +04:00
README.rst Fix six typos and grammar inaccuracies in Rally Readme Files 2015-08-14 16:18:40 +05:30

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, fixtures 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.