summaryrefslogtreecommitdiff
path: root/tests/test_keystone.py
AgeCommit message (Collapse)AuthorFilesLines
2016-09-12Clean imports in codeNguyen Hung Phuong1-2/+2
In some part in the code we import objects. In the Openstack style guidelines they recommend to import only modules. http://docs.openstack.org/developer/hacking/#imports Change-Id: I4b55cae8c2672f82025a95112b14d441d66f9d6d
2016-01-18add unittest code baseJeffrey Zhang1-1/+1
* add a base TestCase class * load the tests from the project root rather than only tests dir * add a test case for WorkerThread builder function Change-Id: Icf878f9249b475a311123c8235c42b1212d02ca6 Partially-implements: bp add-ut-codebase
2016-01-13Add py27 py34 pypy unittestJeffrey Zhang1-0/+2
Change-Id: Iaf58463bd156924839062b8284a2d7151a153db5
2015-07-10Fixed additional OpenStack pep8 issuesBorne Mace1-1/+1
The "hacking" package used in most OpenStack repos pulls in additional pep8 rules. This commit should fix all of them other than a hand full in the build.py file which will be fixed in a separate commit Change-Id: I40a0a30d338592ad64123e3da5523b9ad95a7a9c Partially-Implements: blueprint enable-flake8
2015-05-13Add functional tests to toxJeff Peeler1-0/+25
This adds functional tests to tox, along with a number of prerequisite steps. Since this is primarily a bash project, pbr usage has been avoided. Tests are to be written in python and put in the tests directory. Running tox -e setupenv will execute a setup script (tests/setup_docker.sh) to ensure the running instance of docker meets the minimum version requirement. Running tox -e images will execute the image building script (tools/build-all-docker-images) and will parse the resulting output to report failures. Running tox -e startenv will generate the environment file, run "tools/kolla start", and run first time initialization (eventually). Running tox -e functional is for actually testing the deployed OpenStack environment via a series of tests utilizing the client APIs. Change-Id: Iff6dfdca43f0c44d471e7540a7836e56a0de4507