| commit | a9d5648086d5536490bc8095c2b6d1f43bea0b7d | [log] [tgz] |
|---|---|---|
| author | Avishek Dutta <ad620p@att.com> | Fri Jul 27 16:38:53 2018 +0000 |
| committer | Avishek Dutta <ad620p@att.com> | Fri Jul 27 16:38:53 2018 +0000 |
| tree | 362e059ca13d0e4187ba1b53db9763039f9184e3 | |
| parent | a0b3ba14882b4dc80dbcca90930fecf88ba021e9 [diff] |
Pushing all codes for initial commit
This directory contains Tempest tests to cover the contrail project, as well as a plugin to automatically load these tests into tempest. This is a set of integration tests to be run against a live open-contrail cluster. Tempest has testcases for Contrail API validation, scenarios, and other specific tests useful in validating an open-contrail deployment.
See the tempest plugin docs for information on using it: http://docs.openstack.org/developer/tempest/plugin.html#using-plugins
See the tempest docs for information on writing new tests etc: http://docs.openstack.org/developer/tempest/
To run tungstent-tempest, you must first have Tempest_ installed and configured properly. Please reference Tempest's Quickstart_ guide to do so. Follow all the steps outlined therein. You can install all these includin tempest in a virtual environment. If virtual environment is not installed, then install it using "sud apt-get install python-virtualenv". Afterward, proceed with the steps below.
#. Second, you need to install Patrole. This is done with pip after you check out the Patrole repo. Please reference Patrole''s Quickstart guide for further details::
$ git clone https://git.openstack.org/openstack/patrole $ pip install patrole/
This can be done within a venv.
.. note::
You may also install Patrole from source code by running:: pip install -e patrole/
#. Then you need to install tungsten-fabric This is done with pip after you chekc out the tungsten-tempest repo::
$ git clone https://git.openstack.org/tungsten/tungsten-tempest $ source tempestV/bin/activate $ pip install tungstent_tempest/
This can be done within a venv.
.. note::
You may also install tungsten-fabric from source code by running::
pip install -e tungsten_tempest/
#. Next you must properly configure tempest, which is relatively straightforward. For details on configuring tempest refer to the :ref:tempest-configuration.
#. Next you must properly configure Patrole, which is relatively straightforward. For details on configuring Patrole refer to the :ref:patrole-configuration.
#. Next you must properly configure tungsten-fabric, which is relatively straightforward. For details on configuring tungsten-fabirc refer to the :ref:tungsten-configuration.
#. Once the configuration is done you're now ready to run tungsten-fabric. This can be done using the tempest_run_ command. This can be done by running::
$ tempest run --regex '^tungsten_tempest_plugin\.tests\.api'
There is also the option to use testr directly, or any testr_ based test runner, like ostestr_. For example, from the workspace dir run::
$ stestr --regex '(?!.*\[.*\bslow\b.*\])(^tungsten_tempest_plugin\.tests\.api))'
will run the same set of tests as the default gate jobs.
You can also run tungsten_tempest tests using tox_. To do so, cd into the Tempest directory and run::
$ tox -eall-plugin -- tungstent_tempest_plugin.tests.api
#. Log information from tests is captured in tempest.log under the Tempest repository. Some Patrole debugging information is captured in that log related to expected test results and :ref:role-overriding.
More detailed RBAC testing log output is emitted to tungsten_log. To configure Patrole's logging, see the :ref:tungsten-tempest-configuration guide.
.. _Tempest: https://github.com/openstack/tempest .. _Quickstart: https://docs.openstack.org/tempest/latest/overview.html#quickstart .. _tempest_run: https://docs.openstack.org/tempest/latest/run.html .. _testr: https://testrepository.readthedocs.org/en/latest/MANUAL.html .. _ostestr: https://docs.openstack.org/os-testr/latest/ .. _tox: https://tox.readthedocs.io/en/latest/
To change the role that the tungsten_tempest tests are being run as, edit rbac_test_role in the patrole section of tempest.conf: ::
[patrole] rbac_test_role = member ...
.. note::
The rbac_test_role is service-specific. member, for example, is an arbitrary role, but by convention is used to designate the default non-admin role in the system. Most tunsgtent_tempest tests should be run with admin and member roles. However, other services may use entirely different roles.
For more information about the member role and its nomenclature, please see: <https://ask.openstack.org/en/question/4759/member-vs-_member_/>__.