Switch to refstack-client binary and some cleanup

* Use latest pbr >= 2.0.0
* Removed gitpython as it is not used within the code
* switched to refstack-client binary in README.rst
* Removed unwanted stuff from setup.py as those are already in setup.cfg
* use pip install -e . to auto install dependencies from requirements.txt
  as well as package.

Change-Id: Ia0b1b0a598c48200dc91cc08af9bd78d5685091e
This commit is contained in:
Chandan Kumar 2017-07-25 12:11:58 +05:30
parent 168f814fcb
commit e950efdc73
5 changed files with 20 additions and 15 deletions

View File

@ -58,21 +58,21 @@ Usage
4. Validate your setup by running a short test:: 4. Validate your setup by running a short test::
./refstack-client test -c <Path of the tempest configuration file to use> -v -- --regex tempest.api.identity.v3.test_tokens.TokensV3Test.test_create_token refstack-client test -c <Path of the tempest configuration file to use> -v -- --regex tempest.api.identity.v3.test_tokens.TokensV3Test.test_create_token
5. Run tests. 5. Run tests.
To run the entire API test set:: To run the entire API test set::
./refstack-client test -c <Path of the tempest configuration file to use> -v refstack-client test -c <Path of the tempest configuration file to use> -v
To run only those tests specified in an OpenStack Powered (TM) Guideline:: To run only those tests specified in an OpenStack Powered (TM) Guideline::
./refstack-client test -c <Path of the tempest configuration file to use> -v --test-list <Path or URL of test list> refstack-client test -c <Path of the tempest configuration file to use> -v --test-list <Path or URL of test list>
For example:: For example::
./refstack-client test -c ~/tempest.conf -v --test-list \ refstack-client test -c ~/tempest.conf -v --test-list \
"https://refstack.openstack.org/api/v1/guidelines/2017.01/tests?target=platform&type=required&alias=true&flag=false" "https://refstack.openstack.org/api/v1/guidelines/2017.01/tests?target=platform&type=required&alias=true&flag=false"
This will run only the test cases required by the 2017.01 guidelines This will run only the test cases required by the 2017.01 guidelines
@ -97,7 +97,7 @@ Usage
the ostestr runner as is. This is mainly used for quick verification of the the ostestr runner as is. This is mainly used for quick verification of the
target test cases. (e.g. ``-- --regex tempest.api.identity.v2.test_token``) target test cases. (e.g. ``-- --regex tempest.api.identity.v2.test_token``)
Use ``./refstack-client test --help`` for the full list of arguments. Use ``refstack-client test --help`` for the full list of arguments.
6. Upload your results. 6. Upload your results.
@ -109,7 +109,7 @@ Usage
Following is the command to upload your result anonymously:: Following is the command to upload your result anonymously::
./refstack-client upload <Path of results file> refstack-client upload <Path of results file>
The results file is a JSON file generated by refstack-client when a test has The results file is a JSON file generated by refstack-client when a test has
completed. This is saved in .tempest/.testrepository. When you use the completed. This is saved in .tempest/.testrepository. When you use the
@ -120,7 +120,7 @@ Usage
using an existing subunit file. This requires that you pass in the Keystone using an existing subunit file. This requires that you pass in the Keystone
endpoint URL for the cloud that was tested to generate the subunit data:: endpoint URL for the cloud that was tested to generate the subunit data::
./refstack-client upload-subunit --keystone-endpoint http://some.url:5000/v3 <Path of subunit file> refstack-client upload-subunit --keystone-endpoint http://some.url:5000/v3 <Path of subunit file>
Result can also be uploaded with signature by adding Result can also be uploaded with signature by adding
``-i <path-to-private-key>`` option. Intructions for uploading data with ``-i <path-to-private-key>`` option. Intructions for uploading data with
@ -132,7 +132,7 @@ Usage
You can list previously uploaded data from a RefStack API server by using You can list previously uploaded data from a RefStack API server by using
the following command:: the following command::
./refstack-client list --url <URL of the RefStack API server> refstack-client list --url <URL of the RefStack API server>
Tempest hacking Tempest hacking

View File

@ -2,4 +2,4 @@
cp -r /refstack-client /test cp -r /refstack-client /test
cd /test cd /test
./setup_env ./setup_env
/bin/bash -c ". .venv/bin/activate; exec ./refstack-client test -vv -c tempest.conf -t tempest.api.identity.admin.test_users" /bin/bash -c ". .venv/bin/activate; exec refstack-client test -vv -c tempest.conf -t tempest.api.identity.admin.test_users"

View File

@ -1,4 +1,4 @@
gitpython>=0.3.2.RC1 pbr!=2.1.0,>=2.0.0 # Apache-2.0
python-subunit>=0.0.18 python-subunit>=0.0.18
cryptography>=1.0,!=1.3.0 # BSD/Apache-2.0 cryptography>=1.0,!=1.3.0 # BSD/Apache-2.0
requests>=2.5.2 requests>=2.5.2

View File

@ -16,9 +16,14 @@
import setuptools import setuptools
# In python < 2.7.4, a lazy loading of package `pbr` will break
# setuptools if some other modules registered functions in `atexit`.
# solution from: http://bugs.python.org/issue15881#msg170215
try:
import multiprocessing # noqa
except ImportError:
pass
setuptools.setup( setuptools.setup(
setup_requires=['pbr'], setup_requires=['pbr>=2.0.0'],
version=0.1,
author='David Lenwell',
description='A testing tool used primarily by refstack.',
pbr=True) pbr=True)

View File

@ -157,7 +157,7 @@ python virtualenv.py ${TEMPEST_DIR}/.venv --python="${PYPATH}"
cd .. cd ..
rm -rf virtualenv-${VENV_VERSION} rm -rf virtualenv-${VENV_VERSION}
rm virtualenv-${VENV_VERSION}.tar.gz rm virtualenv-${VENV_VERSION}.tar.gz
${WORKDIR}/.venv/bin/python -m pip install -r ${WORKDIR}/requirements.txt ${WORKDIR}/.venv/bin/python -m pip install -e .
${TEMPEST_DIR}/.venv/bin/python -m pip install -r ${TEMPEST_DIR}/requirements.txt ${TEMPEST_DIR}/.venv/bin/python -m pip install -r ${TEMPEST_DIR}/requirements.txt
# Add additional packages to find more tests by tempest # Add additional packages to find more tests by tempest