Add docs about microversion testing in Tempest

As discussed at the newton midcycle and in the dev
mailing list:

http://lists.openstack.org/pipermail/openstack-dev/2016-July/099860.html

We should add a Tempest test for any microversion that
changes the response schema so we have coverage in Tempest
and also so we don't have to fill large gaps in coverage
in Tempest when adding other unrelated tests.

Change-Id: Ie7cfe7ee857caf630d4380cf673ae208842fbc00
This commit is contained in:
Matt Riedemann 2016-07-22 11:24:44 -04:00
parent 7f84c4e25e
commit 45b21e4503
2 changed files with 13 additions and 3 deletions

View File

@ -356,6 +356,9 @@ necessary to add changes to other places which describe your change:
* Make a new commit to python-novaclient and update corresponding
files to enable the newly added microversion API.
* If the microversion changes the response schema, a new schema and test for
the microversion must be added to Tempest.
Allocating a microversion
-------------------------

View File

@ -201,10 +201,17 @@ Please note:
Microversion API
================
* If an new microversion API is added, the following needs to happen:
If a new microversion API is added, the following needs to happen:
* A new patch for the microversion API change in python-novaclient side
should be submitted.
* A new patch for the microversion API change in python-novaclient side
should be submitted.
* If the microversion changes the response schema, a new schema and test for
the microversion must be added to Tempest. The microversion change in Nova
should not be merged until the Tempest test is submitted and at least
passing; it does not need to be merged yet as long as it is testing the
Nova change via Depends-On. The Nova microversion change commit message
should reference the Change-Id of the Tempest test for reviewers to identify
it.
Release Notes
=============