openstack/tempest
Code Issues Proposed changes

Adapt scenario readme with real-life aspect

Browse Source 
As discussed in the design session a scenario test should be focused on
a real-life use case.

Change-Id: I5cf5518bc7fadfd49b107b93903ab4df093057a1
This commit is contained in:
Marc Koderer 2013-11-08 08:43:35 +01:00
parent 5267d98a62
commit 1b29d835fb
1 changed files with 7 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
tempest/scenario/README.rst
View File

@ -10,10 +10,13 @@ function. Complicated setups where one part might depend on completion
of a previous part. They ideally involve the integration between of a previous part. They ideally involve the integration between
multiple OpenStack services to exercise the touch points between them. multiple OpenStack services to exercise the touch points between them.
An example would be: start with a blank environment, upload a glance Any scenario test should have a real-life use case. An example would be:
image, deploy a vm from it, ssh to the guest, make changes, capture
that vm's image back into glance as a snapshot, and launch a second vm - "As operator I want to start with a blank environment":
from that snapshot. 1. upload a glance image
2. deploy a vm from it
3. ssh to the guest
4. create a snapshot of the vm
Why are these tests in tempest? Why are these tests in tempest?