Skip to content

Commit 72d6239

Browse files
javierlozallujavierlozallu
authored
Merge pull request #211 from camaraproject/sergiofranciscoortiz-patch-3
Gherkin Test feature file for EdgeCloud_LCM
2 parents f8d777e + 9f38e2e commit 72d6239

File tree

1 file changed

+134
-0
lines changed

1 file changed

+134
-0
lines changed

‎code/Test_definitions/Edgecloud_LCM_Test.feature

+134
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
#/*- ---license-start
2+
#* CAMARA Project
3+
#* ---
4+
#* Copyright (C) 2022 - 2023 Contributors | Deutsche Telekom AG to CAMARA a Series of LF Projects, LLC
5+
#* The contributor of this file confirms his sign-off for the
6+
#* Developer Certificate of Origin (http://developercertificate.org).
7+
#* ---
8+
#* Licensed under the Apache License, Version 2.0 (the "License");
9+
#* you may not use this file except in compliance with the License.
10+
#* You may obtain a copy of the License at
11+
#*
12+
#* http://www.apache.org/licenses/LICENSE-2.0
13+
#*
14+
#* Unless required by applicable law or agreed to in writing, software
15+
#* distributed under the License is distributed on an "AS IS" BASIS,
16+
#* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
17+
#* See the License for the specific language governing permissions and
18+
#* limitations under the License.
19+
#* ---license-end
20+
#*/
21+
22+
@EdgeCloudLCM @EdgeCloudLCMSanity
23+
Feature:Automated Edge Cloud API System Integration Test
24+
25+
26+
@EdgeCloud_LCM_app_submittion_ok
27+
Scenario: Submit an Application with mandatory parameters
28+
When invoking with the POST method to submit an app with all required parameters
29+
Then response code is 201
30+
31+
@EdgeCloud_LCM_app_submittion_conflict
32+
Scenario: Submit an Application with mandatory parameters
33+
Given an aplication with the same name and version had already been submitted
34+
When invoking with the POST method to submit an app with all required parameters
35+
Then response code is 409
36+
37+
@EdgeCloud_LCM_app_get_info_valid_parameter
38+
Scenario: Get application info with mandatory parameter ("appId")
39+
When invoking the GET method to obtain app information with mandatory parameter ("appId")
40+
Then response code is 200
41+
42+
@EdgeCloud_LCM_app_get_info_invalid_parameter
43+
Scenario: Get application info with mandatory parameter ("appId")
44+
Given appId provided does not exist
45+
When invoking the GET method to obtain submittion app information with mandatory parameter ("appId")
46+
Then response code is 404
47+
48+
@EdgeCloud_LCM_app_delete_valid_parameter
49+
Scenario: Delete all the information and content related to an Application with mandatory parameter ("appId")
50+
Given there are no running instances of the app
51+
When invoking with the DELETE method to delete an app with just mandatory parameter ("appId")
52+
Then response code is 202
53+
And the application information is deleted
54+
55+
@EdgeCloud_LCM_app_delete_conflict
56+
Scenario: Delete all the information and content related to an Application with mandatory parameter ("appId")
57+
Given there are running instances of the app
58+
When invoking with the DELETE method to delete an app with just mandatory parameter ("appId")
59+
Then response code is 409
60+
61+
@EdgeCloud_LCM_app_delete_invalid_parameter
62+
Scenario: Delete all the information and content related to an Application with mandatory parameter ("appId")
63+
Given appId provided does not exist
64+
When invoking with the DELETE method to delete an app with just mandatory parameter ("appId")
65+
Then response code is 404
66+
67+
@EdgeCloud_LCM_app_instantiation_ok_mandatory_parameters
68+
Scenario: Instantiate an Application with just mandatory parameters ("appId" in path, and "region" in body)
69+
Given an aplication has already been submitted
70+
When invoking with the POST method to instantiate an app with just mandatory parameters ("appId" in path, and "region" in body)
71+
Then response code is 202
72+
And the process of instantiating the app starts in all available edge cloud zones in the region provided
73+
74+
@EdgeCloud_LCM_app_instantiation_ok_optional_parameters
75+
Scenario: Instantiate an Application with mandatory parameters ("appId" in path, and "region" in body) and optional parameter ("EdgeCloudZone")
76+
Given an aplication has already been submitted
77+
When invoking with the POST method to instantiate an app with mandatory mandatory parameters ("appId" in path, and "region" in body) and optional parameter ("EdgeCloudZone")
78+
Then response code is 202
79+
And the process of intantiating the app starts only in given region and edge cloud zone
80+
81+
@EdgeCloud_LCM_app_instantiation_conflict
82+
Scenario: Instantiate an Application with mandatory parameters ("appId" in path, and "region" in body) and optional parameter ("EdgeCloudZone")
83+
Given an aplication has already been submitted, but already instantiated in given EdgeCloudZone
84+
When invoking with the POST method to instantiate an app with mandatory mandatory parameters ("appId" in path, and "region" in body) and optional parameter ("EdgeCloudZone")
85+
Then response code is 409
86+
87+
@EdgeCloud_LCM_app_instance_get_info_valid_parameter
88+
Scenario: Get application instance info with mandatory parameter ("appId")
89+
When invoking the GET method to obtain information an app instance with mandatory parameter ("appId")
90+
Then response code is 200
91+
And information of all existing app instances of given app is returned
92+
93+
@EdgeCloud_LCM_app_instance_get_info_invalid_parameter
94+
Scenario: Get application instance info with mandatory parameter ("appId")
95+
Given appId provided does not exist
96+
When invoking the GET method to obtain information an app instance with mandatory parameter ("appId")
97+
Then response code is 404
98+
99+
@EdgeCloud_LCM_app_innstance_delete_all_instances
100+
Scenario: Delete all running instances of an application in Edge Cloud
101+
When invoking with the DELETE method to terminate running instances of an application within Edge Cloudwith with just mandatory parameter ("appId")
102+
Then response code is 202
103+
And all the application instances termination initiated
104+
105+
@EdgeCloud_LCM_app_innstance_delete_valid_parameter
106+
Scenario: Delete a running instance of an application within an Edge Cloud Zone with optional parameter ("appInstanceId")
107+
When invoking with the DELETE method to terminate a running instance of an application including optional parameter ("appInstanceId") and mandatory parameter ("appId")
108+
Then response code is 202
109+
And the application instance termination initiated
110+
111+
112+
@EdgeCloud_LCM_app_innstance_delete_invalid_parameter
113+
Scenario: Delete a running instance of an application within an Edge Cloud Zone with optional parameter ("appInstanceId")
114+
Given appInstanceId provided does not exist
115+
When invoking with the DELETE method to terminate a running instance of an application including optional parameter ("appInstanceId") and mandatory parameter ("appId")
116+
Then response code is 404
117+
118+
@EdgeCloud_LCM_get_all_edge_cloud_zones_ok
119+
Scenario: Get information of all existing Edge Cloud Zones
120+
When invoking the GET method to obtain information of Edge Cloud Zones with no optional parameters
121+
Then response code is 200
122+
And information of all existing edge cloud zones is returned
123+
124+
@EdgeCloud_LCM_get_filtered_edge_cloud_zones_ok
125+
Scenario: Get information of existing Edge Cloud Zones with optional parameters ("region","status")
126+
When invoking the GET method to obtain information of Edge Cloud Zones with a region and a status (active,inactive,unknown)
127+
Then response code is 200
128+
And only information of cloud zones in the region and with the current status given in the input is returned
129+
130+
@EdgeCloud_LCM_get_filtered_edge_cloud_zones_nok
131+
Scenario: Get information of existing Edge Cloud Zones with optional parameters ("region","status")
132+
Given region provided that not exist
133+
When invoking the GET method to obtain information of Edge Cloud Zones with a region and a status (active,inactive,unknown)
134+
Then response code is 404

0 commit comments

Comments
 (0)