RETIRED, further work has moved to Debian project infrastructure
a12701cf32
This is an example using xml parsing in existing unit tests instead of assertIn and string comparisons to verify workflow generation. It's much less fragile. If folks like this, we can change other tests similarly. Change-Id: Ib1c266933a4a3104af34586527148c2612019000 |
||
---|---|---|
doc/source | ||
etc | ||
sahara | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
OpenStack Data Processing ("Sahara") project
Sahara at wiki.openstack.org: https://wiki.openstack.org/wiki/Sahara
Launchpad project: https://launchpad.net/sahara
Sahara docs site: http://docs.openstack.org/developer/sahara
Roadmap: https://wiki.openstack.org/wiki/Sahara/Roadmap
Quickstart guide: http://docs.openstack.org/developer/sahara/devref/quickstart.html
How to participate: http://docs.openstack.org/developer/sahara/devref/how_to_participate.html
License
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0