Go to file

Bartłomiej Piotrowski 6270ce08c7 Allow to specify multiple tests in run_tests.sh

Disable checking for unbound variables, as there is possibility that no
tests were specified. Example invocation:

run_tests.sh -n -t fuelclient/tests/test_client.py:TestAuthentication.test_wrong_credentials \
-t fuelclient/tests/test_client.py:TestDownloadUploadNodeAttributes

Additionally align shifts in getopt loop and remove
dead return from tox invocation.

DocImpact
Change-Id: I83a52b5f5467c9ea92dfafba9b92b700f7e76a38
Closes-Bug: 1420664

2015-03-02 12:07:38 +01:00

fuelclient

Merge "Add start parameter for tasks execution"

2015-02-12 08:53:11 +00:00

.gitignore

Add .gitignore and .gitreview

2015-01-13 11:57:41 +01:00

.gitreview

Add .gitignore and .gitreview

2015-01-13 11:57:41 +01:00

fuel

Fuelclient major refactoring

2014-04-10 15:23:25 +04:00

MANIFEST.in

Basic profiling facilities for CLI

2014-11-14 13:24:09 +01:00

README.rst

Add a README file

2015-01-24 06:40:06 +01:00

requirements.txt

Allow python-fuelclient to be packaged properly

2015-01-24 22:57:34 +01:00

run_tests.sh

Allow to specify multiple tests in run_tests.sh

2015-03-02 12:07:38 +01:00

setup.cfg

Run tests under Python-2.7

2015-02-13 10:31:17 +01:00

setup.py

Allow python-fuelclient to be packaged properly

2015-01-24 22:57:34 +01:00

test-requirements.txt

Allow python-fuelclient to be packaged properly

2015-01-24 22:57:34 +01:00

tox.ini

Allow python-fuelclient to be packaged properly

2015-01-24 22:57:34 +01:00

README.rst

python-fuelclient

python-fuelclient provides a CLI tool and a Python API wrapper for interacting with Fuel.

Project resources

Project status, bugs, and blueprints are tracked on Launchpad:: https://launchpad.net/fuel
Development documentation is hosted here:: http://docs.mirantis.com/fuel-dev
User guide can be found here:: http://docs.mirantis.com
Any additional information can be found on the Fuel's project wiki: https://wiki.openstack.org/wiki/Fuel

Anyone wishing to contribute to python-fuelclient should follow the general OpenStack process. A good reference for it can be found here: https://wiki.openstack.org/wiki/How_To_Contribute

http://docs.openstack.org/infra/manual/developers.html