cf9f7f239a
Move the "developing bindep" guide from README.rst to CONTRIBUTING.rst where it fits a bit better. Change-Id: Ic98defa0cc7187e47eb1a5374f55cf3e7e0f6680
52 lines
2.1 KiB
ReStructuredText
52 lines
2.1 KiB
ReStructuredText
Contribution Overview
|
|
=====================
|
|
|
|
If you would like to contribute to the development of OpenStack, you must
|
|
follow the steps in this page:
|
|
|
|
http://docs.openstack.org/infra/manual/developers.html
|
|
|
|
If you already have a good understanding of how the system works and your
|
|
OpenStack accounts are set up, you can skip to the development workflow
|
|
section of this documentation to learn how changes to OpenStack should be
|
|
submitted for review via the Gerrit tool:
|
|
|
|
http://docs.openstack.org/infra/manual/developers.html#development-workflow
|
|
|
|
Pull requests submitted through GitHub will be ignored.
|
|
|
|
Bugs should be filed on StoryBoard, not GitHub:
|
|
|
|
https://storyboard.openstack.org/#!/project/811
|
|
|
|
Developing bindep
|
|
=================
|
|
|
|
Either install `bindep` and run ``bindep test`` to check you have the needed
|
|
tools, or review ``bindep.txt`` by hand.
|
|
|
|
Running Tests
|
|
-------------
|
|
|
|
The testing system is based on a combination of tox and testr. The canonical
|
|
approach to running tests is to simply run the command `tox`. This will
|
|
create virtual environments, populate them with dependencies and run all of
|
|
the tests that OpenStack CI systems run. Behind the scenes, tox is running
|
|
`testr run --parallel`, but is set up such that you can supply any additional
|
|
testr arguments that are needed to tox. For example, you can run:
|
|
`tox -- --analyze-isolation` to cause tox to tell testr to add
|
|
--analyze-isolation to its argument list.
|
|
|
|
It is also possible to run the tests inside of a virtual environment
|
|
you have created, or it is possible that you have all of the dependencies
|
|
installed locally already. If you'd like to go this route, the requirements
|
|
are listed in requirements.txt and the requirements for testing are in
|
|
test-requirements.txt. Installing them via pip, for instance, is simply::
|
|
|
|
pip install -r requirements.txt -r test-requirements.txt
|
|
|
|
In you go this route, you can interact with the testr command directly.
|
|
Running `testr run` will run the entire test suite. `testr run --parallel`
|
|
will run it in parallel (this is the default incantation tox uses.) More
|
|
information about testr can be found at: http://wiki.openstack.org/testr
|