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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
|
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) opnfv
==========================================
VIM identity operations test specification
==========================================
.. toctree::
:maxdepth: 2
Scope
=====
The VIM identity test area evaluates the ability of the system under test to
support VIM identity operations. The tests in this area will evaluate
API discovery operations within the Identity v3 API, auth operations within
the Identity API.
References
================
- OpenStack interoperability guidelines (version 2016.08)
- https://github.com/openstack/interop/blob/master/2016.08.json
- Openstack interoperability
- https://www.openstack.org/brand/interop/
- OpenStack interoperability test cases excluding object storage
- https://refstack.openstack.org/api/v1/guidelines/2016.08/tests?target=compute&type=required&alias=true&flag=false
Definitions and abbreviations
=============================
The following terms and abbreviations are used in conjunction with this test area
- API - Application Programming Interface
- NFVi - Network Functions Virtualisation infrastructure
- VIM - Virtual Infrastructure Manager
System Under Test (SUT)
=======================
The system under test is assumed to be the NFVi and VIM in operation on an Pharos compliant infrastructure.
Test Area Structure
====================
The test area is structured based on VIM identity operations. Each test case
is able to run independently, i.e. irrelevant of the state created by a previous test.
All these test cases are included in the test case dovetail.osinterop.tc001 of
cvp test suite.
Dependency Description
======================
The VIM identity operations test cases are a part of the OpenStack
interoperability tempest test cases. For Danube based dovetail release, the
OpenStack interoperability guidelines (version 2016.08) is adopted, which is
valid for Kilo, Liberty, Mitaka and Newton releases of Openstack.
Test Descriptions
=================
----------------------------------------------------
API discovery operations within the Identity v3 API
----------------------------------------------------
Use case specification
-----------------------
tempest.api.identity.v3.TestApiDiscovery.test_api_version_resources
tempest.api.identity.v3.TestApiDiscovery.test_api_media_types
tempest.api.identity.v3.TestApiDiscovery.test_api_version_statuses
tempest.api.identity.v3.test_api_discovery.TestApiDiscovery.test_api_version_resources
tempest.api.identity.v3.test_api_discovery.TestApiDiscovery.test_api_media_types
tempest.api.identity.v3.test_api_discovery.TestApiDiscovery.test_api_version_statuses
note: the latter three test cases are the alias of the former three, respectively.
alias should always be included so that the test run will be tempest version agnostic,
which can be used to test different version of Openstack.
Test preconditions
-------------------
None
Basic test flow execution description and pass/fail criteria
------------------------------------------------------------
Test execution
'''''''''''''''
* Test action 1: Show the v3 identity api description, the test passes if keys
'id', 'links', 'media-types', 'status', 'updated' are all included in the description
response message.
* Test action 2: Get the value of v3 identity api 'media-types', the test passes if
api version 2 and version 3 are all included in the response.
* Test action 3: Show the v3 indentity api description, the test passes if 'current',
'stable', 'experimental', 'supported', 'deprecated' are all of the identity api 'status'
values.
Pass / fail criteria
'''''''''''''''''''''
This test case passes if all test action steps execute successfully and all assertions
are affirmed. If any test steps fails to execute successfully or any of the assertions
is not met, the test case fails.
Post conditions
---------------
None
------------------------------------------
Auth operations within the Identity API
------------------------------------------
Use case specification
-----------------------
tempest.api.identity.v3.test_tokens.TokensV3Test.test_create_token
Test preconditions
-------------------
None
Basic test flow execution description and pass/fail criteria
------------------------------------------------------------
Test execution
'''''''''''''''
* Test action 1: Get the token by system credentials, the test passes if
the returned token_id is not empty and is string type.
* Test action 2: Get the user_id in getting token response message, the test
passes if it is equal to the user_id which is used to get token.
* Test action 3: Get the user_name in getting token response message, the test
passes if it is equal to the user_name which is used to get token.
* Test action 4: Get the method in getting token response message, the test
passes if it is equal to the password which is used to get token.
Pass / fail criteria
'''''''''''''''''''''
This test case passes if all test action steps execute successfully and all assertions
are affirmed. If any test steps fails to execute successfully or any of the assertions
is not met, the test case fails.
Post conditions
---------------
None
|
