summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/testspecification/tempest_volume/index.rst
blob: 80af54fae40b29a456c392fcabcbe9410f076008 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) Ericsson AB

===========================================
Tempest Volume test specification
===========================================


Scope
=====

This test area evaluates the ability of a system under test to manage volumes.

The test area specifically validates the creation, the deletion and
the attachment/detach volume operations.
tests.


References
==========

N/A

System Under Test (SUT)
=======================

The system under test is assumed to be the NFVi and VIM in operation on a
Pharos compliant infrastructure.

Test Area Structure
===================

The test area is structured in individual tests as listed below.
For detailed information on the individual steps and assertions performed
by the tests, review the Python source code accessible via the following links:

All these test cases are included in the test case dovetail.tempest.volume of
OVP test suite.


`Attach Detach Volume to Instance <https://github.com/openstack/tempest/blob/master/tempest/api/volume/test_volumes_actions.py>`_
    - tempest.api.volume.test_volumes_actions.VolumesActionsTest.test_attach_detach_volume_to_instance


`Volume Boot Pattern test <https://github.com/openstack/tempest/blob/master/tempest/scenario/test_volume_boot_pattern.py>`_
    - Create in Cinder some bootable volume importing a Glance image
    - Boot an instance from the bootable volume
    - Write content to the volume
    - Delete an instance and Boot a new instance from the volume
    - Check written content in the instance
    - Create a volume snapshot while the instance is running
    - Boot an additional instance from the new snapshot based volume
    - Check written content in the instance booted from snapshot

- tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern