Merge branch '4.4.1-dev-SOL002-VNFConfiguration' into '4.4.1-dev' (b2a60247) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFConfiguration-API/ApiVersion.robot

+10 −10

Original line number	Diff line number	Diff line
		@@ -11,7 +11,7 @@ POST API Version - Method not implemented
		... Test title: POST API version - Method not implemented
		... Test objective: The objective is to test that POST method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -23,7 +23,7 @@ GET API Version
		... Test title: GET API Version
		... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -36,7 +36,7 @@ PUT API Version - Method not implemented
		... Test title: PUT API Version - Method not implemented
		... Test objective: The objective is to test that PUT method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -48,7 +48,7 @@ PATCH API Version - Method not implemented
		... Test title: PATCH API Version - Method not implemented
		... Test objective: The objective is to test that PATCH method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -60,7 +60,7 @@ DELETE API Version - Method not implemented
		... Test title: DELETE API Version - Method not implemented
		... Test objective: The objective is to test that DELETE method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -72,7 +72,7 @@ POST API Version with apiMajorVerion - Method not implemented
		... Test title: POST API version with apiMajorVerion - Method not implemented
		... Test objective: The objective is to test that POST method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.1 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -84,7 +84,7 @@ GET API Version with apiMajorVerion
		... Test title: GET API Version with apiMajorVerion
		... Test objective: The objective is to test that GET method successfully return ApiVersionInformation
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.2 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -97,7 +97,7 @@ PUT API Version with apiMajorVerion - Method not implemented
		... Test title: PUT API Version with apiMajorVerion - Method not implemented
		... Test objective: The objective is to test that PUT method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.3 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -109,7 +109,7 @@ PATCH API Version with apiMajorVerion - Method not implemented
		... Test title: PATCH API Version with apiMajorVerion - Method not implemented
		... Test objective: The objective is to test that PATCH method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.4 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none
		@@ -121,7 +121,7 @@ DELETE API Version with apiMajorVerion - Method not implemented
		... Test title: DELETE API Version with apiMajorVerion - Method not implemented
		... Test objective: The objective is to test that DELETE method is not implemented
		... Pre-conditions: none
		... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.3.1
		... Reference: Clause 9.3.3.3.5 - ETSI GS NFV-SOL 013 [5] v4.4.1
		... Config ID: Config_prod_VNFM
		... Applicability: none
		... Post-Conditions: none

SOL002/VNFConfiguration-API/Configuration.robot

+9 −9

Original line number	Diff line number	Diff line
		@@ -13,7 +13,7 @@ Set new VNF Configuration
		... Test title: Set a new VNF Configuration
		... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
		... Pre-conditions: A VNF instance is instantiated
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
		@@ -29,7 +29,7 @@ Get information about a VNF configuration
		... Test title: Get information about a VNF configuration
		... Test objective: The objective is to test the retrieval of an existing VNF instance configuration and perform a JSON schema validation of the collected configuration data structure
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured.
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -43,7 +43,7 @@ Get information about a VNF configuration with HTTP Etag
		... Test title: Get information about a VNF configuration with HTTP Etag
		... Test objective: The objective is to test the retrieval of an existing VNF instance configuration, check the generation by the VNF of an HTTP Etag opaque identifier, and perform a JSON schema validation of the collected configuration data structure
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.2 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: none
		@@ -58,7 +58,7 @@ Set new VNF Configuration - HTTP Etag precondition unsuccessful
		... Test title: Set a new VNF Configuration - HTTP Etag precondition unsuccessful
		... Test objective: The objective is to test the unsuccess in setting a duplication of VNF configuration identified by an already used HTTP Etag identifier. The test also checks the JSON schema of the unsuccessful operation HTTP response.
		... Pre-conditions: A VNF instance is instantiated. The VNF instance is already configured (Test ID 6.3.1.1.1) with a given HTTP Etag identifier.
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The VNF configuration is not modified by the unsuccessful operation and it matches the configuration issued in Test ID 6.3.1.1.1
		@@ -72,7 +72,7 @@ POST VNF Configuration - Method not implemented
		... Test title: POST VNF Configuration - Method not implemented
		... Test objective: The objective is to test that POST method is not allowed to create a new VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -84,7 +84,7 @@ PUT VNF Configuration - Method not implemented
		... Test title: PUT VNF Configuration - Method not implemented
		... Test objective: The objective is to test that PUT method is not allowed to modify an existing VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.3 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -96,7 +96,7 @@ DELETE VNF Configuration - Method not implemented
		... Test title: Delete VNF Configuration - Method not implemented
		... Test objective: The objective is to test that DELETE method is not allowed to delete an existing VNF configuration
		... Pre-conditions: none
		... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.5 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: none
		... Post-Conditions: none
		@@ -108,7 +108,7 @@ Set new VNF Configuration With Attribute vnfConfigurationData
		... Test title: Set a new VNF Configuration with Attribute vnfConfigurationData
		... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
		... Pre-conditions: A VNF instance is instantiated
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration
		@@ -123,7 +123,7 @@ Set new VNF Configuration With Attribute vnfcConfigurationData
		... Test title: Set a new VNF Configuration with Attribute vnfcConfigurationData
		... Test objective: The objective is to test the creation of a new VNF configuration and perform a JSON schema validation of the returned configuration data structure
		... Pre-conditions: A VNF instance is instantiated
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.3.1
		... Reference: Clause 9.4.2.3.4 - ETSI GS NFV-SOL 002 [2] v4.4.1
		... Config ID: Config_prod_VE
		... Applicability: The VNF supports the generation of HTTP Etag opaque identifiers
		... Post-Conditions: The configuration is successfully set in the VNF and it matches the issued configuration

SOL002/VNFConfiguration-API/jsons/vnfConfigModifications.json

+0 −1

Original line number	Diff line number	Diff line
		@@ -35,7 +35,6 @@
		]
		}
		],
		"dhcpServer": "string",
		"vnfcSpecificData": {}
		}
		],

SOL002/VNFConfiguration-API/jsons/vnfConfigModificationsWithvnfcConfigurationData.json

+0 −1

Original line number	Diff line number	Diff line
		@@ -18,7 +18,6 @@
		]
		}
		],
		"dhcpServer": "string",
		"vnfcSpecificData": {}
		}
		],

SOL002/VNFConfiguration-API/schemas/vnfConfigModifications.schema.json

+0 −5

Original line number	Diff line number	Diff line
		@@ -200,11 +200,6 @@
		}
		}
		},
		"dhcpServer": {
		"description": "An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons.\n",
		"type": "string",
		"format": "IP"
		},
		"vnfcSpecificData": {
		"description": "This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of keyvalue pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259. In the following example, a list of key-value pairs with four keys (\"aString\", \"aNumber\", \"anArray\" and \"anObject\") is provided to illustrate that the values associated with different keys can be of different type.\n",
		"type": "object"