SOL002 VNF Configuration API completed (5bd9a483) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL002/VNFConfiguration-API_egm/Configuration.robot

0 → 100644

+91 −0

Original line number	Diff line number	Diff line
		* Settings *
		Resource variables.txt
		Library REST ${VNF_SCHEMA}://${VNF_HOST}:${VNF_PORT}
		... spec=SOL002-VNFConfiguration-API.yaml
		Library JSONLibrary
		Library JSONSchemaLibrary schemas/
		Library OperatingSystem
		Library DependencyLibrary

		* Variables *
		${Etag}= an etag
		${Etag_modified}= a modified etag

		* Test cases *
		POST Configuration - Method not implemented
		log Trying to perform a POST. This method should not be implemented
		Set Headers {"Accept":"${ACCEPT}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		Post ${apiRoot}/${apiName}/${apiVersion}/configuration
		Log Validate Status code
		Integer response status 405

		Get information about a configuration
		Log Query VNF The GET method queries information about a configuration.
		Set Headers {"Accept":"${ACCEPT}"}
		Set Headers {"Content-Type": "${CONTENT_TYPE}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		Log Execute Query and validate response
		Get ${apiRoot}/${apiName}/${apiVersion}/configuration
		${Etag}= Output response headers Etag
		Log Validate Status code
		Integer response status 200
		${contentType}= Output response headers Content-Type
		Should Contain ${contentType} ${CONTENT_TYPE}
		${result}= Output response body
		${json}= evaluate json.loads('''${result}''') json
		Validate Json vnfConfiguration.schema.json ${json}
		Log Validation OK

		PUT Config - Method not implemented
		log Trying to perform a PUT. This method should not be implemented
		Set Headers {"Accept":"${ACCEPT}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		Put ${apiRoot}/${apiName}/${apiVersion}/configuration
		Log Validate Status code
		Integer response status 405

		PATCH Config
		log Trying to perform a PATCH. This method modifies the configuration
		Set Headers {"Accept":"${ACCEPT}"}
		Set Headers {"Content-Type": "${CONTENT_TYPE}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		${body}= Get File json/vnfConfigModifications.json
		Patch ${apiRoot}/${apiName}/${apiVersion}/configuration ${body}
		Log Validate Status code
		${Etag_modified}= Output response headers Etag
		Integer response status 200
		${contentType}= Output response headers Content-Type
		Should Contain ${contentType} ${CONTENT_TYPE}
		${result}= Output response body
		${json}= evaluate json.loads('''${result}''') json
		Validate Json vnfConfigModifications.schema.json ${json}
		Log Validation OK

		PATCH Config - Precondition failed
		[Documentation] Precondition Failed
		... Precondition Failed A precondition given in an HTTP request header is not fulfilled.
		... Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.
		... The response body should contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error.
		Depends On Test PATCH Alarm # If the previous test scceeded, it means that Etag has been modified
		log Trying to perform a PATCH. This method modifies an individual alarm resource
		Set Headers {"Accept":"${ACCEPT}"}
		Set Headers {"Content-Type": "${CONTENT_TYPE}"}
		Set Headers {"If-Match": "${Etag}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		${body}= Get File json/vnfConfigModifications.json
		Patch ${apiRoot}/${apiName}/${apiVersion}/configuration ${body}
		Log Validate Status code
		Integer response status 412
		${problemDetails}= Output response body
		${json}= evaluate json.loads('''${problemDetails}''') json
		Validate Json ProblemDetails.schema.json ${json}
		Log Validation OK

		DELETE Config - Method not implemented
		log Trying to perform a DELETE. This method should not be implemented
		Set Headers {"Accept":"${ACCEPT}"}
		Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"}
		Delete ${apiRoot}/${apiName}/${apiVersion}/configuration
		Log Validate Status code
		Integer response status 405
		No newline at end of file

SOL002/VNFConfiguration-API_egm/SOL002-VNFConfiguration-API.json

0 → 100644

+1398 −0

File added.

Preview size limit exceeded, changes collapsed.

SOL002/VNFConfiguration-API_egm/SOL002-VNFConfiguration-API.yaml

0 → 100644

+2202 −0

File added.

Preview size limit exceeded, changes collapsed.

SOL002/VNFConfiguration-API_egm/jsons/vnfConfigModifications.json

0 → 100644

+43 −0

Original line number	Diff line number	Diff line
		{
		"vnfConfigurationData": {
		"extCpConfig": {
		"cpId": "string",
		"cpdId": "string",
		"addresses": [
		{
		"address": {
		"macAddress": "string",
		"ipAddress": "string"
		},
		"useDynamicAddress": true,
		"port": 0
		}
		]
		},
		"dhcpServer": "string",
		"vnfSpecificData": {}
		},
		"vnfcConfigurationData": [
		{
		"vnfcInstanceId": "string",
		"intCpConfig": [
		{
		"cpId": "string",
		"cpdId": "string",
		"addresses": [
		{
		"address": {
		"macAddress": "string",
		"ipAddress": "string"
		},
		"useDynamicAddress": true,
		"port": 0
		}
		]
		}
		],
		"dhcpServer": "string",
		"vnfcSpecificData": {}
		}
		]
		}
		No newline at end of file

SOL002/VNFConfiguration-API_egm/schemas/problemDetails.schema.json

0 → 100644

+34 −0

Original line number	Diff line number	Diff line
		{
		"definitions": {},
		"$schema": "http://json-schema.org/draft-07/schema#",
		"type": "object",
		"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
		"properties": {
		"type": {
		"type": "string",
		"description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",
		"format": "URI"
		},
		"title": {
		"type": "string",
		"description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n"
		},
		"status": {
		"type": "integer",
		"description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n"
		},
		"detail": {
		"type": "string",
		"description": "A human-readable explanation specific to this occurrence of the problem.\n"
		},
		"instance": {
		"type": "string",
		"description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",
		"format": "URI"
		}
		},
		"required": [
		"status",
		"detail"
		]
		}
		No newline at end of file