ad5c4b83f3
This patch expands the CTI documentation to support multiple languages. It creates a single page that describes overall CTI goals, and then links to documents that go into specifics on each language supported in OpenStack. The Javascript section is new, and includes documentation for the current state of the Javascript CTI. It also explicitly calls out areas where work needs to be done, in order to encourage discussion and contributions. Change-Id: I971b9271443e4fd227b4a6b347dfc385b67eb3e4 Depends-On: I00186c9af441c1778a22379634cdb2f918324bd8
39 lines
1.2 KiB
ReStructuredText
39 lines
1.2 KiB
ReStructuredText
============================
|
|
Consistent Testing Interface
|
|
============================
|
|
|
|
OpenStack has a lot of projects. For each project, the OpenStack CI system
|
|
needs to be able to perform a lot of tasks. If each project has a slightly
|
|
different way to accomplish those tasks, it makes the management of a
|
|
consistent testing infrastructure very difficult to deal with. Additionally,
|
|
because of the high volume of development changes and testing, the testing
|
|
infrastructure has to be able to pre-cache artifacts that are normally fetched
|
|
over the internet. To that end, each project should support a consistent
|
|
interface for driving tests and other necessary tasks.
|
|
|
|
The following tasks are required for every project. Every project must:
|
|
|
|
- Execute tests
|
|
- Enforce code style
|
|
- Generate a code coverage report
|
|
- Generate a source tarball
|
|
- Generate documentation
|
|
|
|
The following are other common tasks, which may not be relevant for every
|
|
project:
|
|
|
|
- Enforce code coverage
|
|
- Generate a release artifact
|
|
- Publish a release artifact
|
|
- Import translation strings
|
|
- Export translation strings
|
|
|
|
Tools and approaches vary by language, please choose which language is
|
|
relevant to you.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
:glob:
|
|
|
|
cti/*
|