openstack/tempest
Code Issues Proposed changes

Add README section about API stability

Browse Source 
This commit adds a section to the README outlining that tempest tests
should only be added for stable APIs. If the API is tested the
expectation is that it complies with the API stability guidelines.

Change-Id: I02a93f66ff45e4d687b7395fb24ee5bda6e52fb0
This commit is contained in:
Matthew Treinish 2014-06-05 15:40:33 -04:00
parent cd7bf6249f
commit 3eb7a892d9
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.rst
View File

@ -176,3 +176,11 @@ If a test is being added for a feature that exists in all the current releases
of the projects then the only concern is that the API behavior is the same of the projects then the only concern is that the API behavior is the same
across all the versions of the project being tested. If the behavior is not across all the versions of the project being tested. If the behavior is not
consistent the test will not be able to merge. consistent the test will not be able to merge.
API Stability
-------------
For new tests being added to Tempest the assumption is that the API being
tested is considered stable and adheres to the OpenStack API stability
guidelines. If an API is still considered experimental or in development then
it should not be tested by Tempest until it is considered stable.