Make the scenario test spec release independent

And fix a few inconsistencies with test
scenario #7 and call for new contributions

Change-Id: I760d22cb6ef90d05eaabd8aeddfbc2e145cee1c9
Partially-implements: bp scenario-tests
This commit is contained in:
Nir Gilboa 2018-02-20 22:39:21 +02:00 committed by Goutham Pacha Ravi
parent 4d69ce3206
commit 49b3bb274e
2 changed files with 21 additions and 5 deletions

View File

@ -16,6 +16,18 @@ the Ocata release. The agreed upon specs are listed here:
priorities/*
Release Independent specs
=========================
These specifications can be implemented over multiple releases.
.. toctree::
:glob:
:maxdepth: 1
specs/release_independent/*
Rocky approved specs
=====================
.. toctree::

View File

@ -586,10 +586,11 @@ _`7) Create/manage share and snapshot and write data`
- Delete share S1
- ok, deleted
* - 18
- Try manage share S1 again
- fail, resource not found
- Try manage share S1 again as S2, this should fail asynchronously
since the resource is gone
- S2 has a status set to 'error'
* - 19
- Delete S1
- Delete S2
- ok, deleted
* - 20
- Delete UVM
@ -1045,13 +1046,16 @@ Implementation
Assignee(s)
-----------
Primary assignee:
Original assignee:
* vponomaryov
Other contributors:
* TBD
* We're inviting more contributors to continue to improve scenario tests.
Adding new scenario test cases to manila-tempest-plugin does *not* require
adding the test case description to this spec, but it is encouraged if you
like feedback for your new test cases.
Work Items
----------