[test-new][SOL025][DATA-ANALYTICS][v5.2.1][12.3.1.2.x Test-IDs] Implement new... (ecb994d9) · Commits · NFV - Network Functions Virtualisation / api-tests

SOL025/TelcoCloudDataAnalyticsService-API/IndividualTelco-CloudDataAnalytics.robot

0 → 100644

+137 −0

Original line number	Diff line number	Diff line
		* Settings *
		Resource environment/variables.txt
		Resource DataAnalyticsOperationKeywords.robot
		Library REST
		... ${TCDAS_SCHEMA}://${TCDAS_HOST}:${TCDAS_PORT}
		... ssl_verify=false
		Library OperatingSystem
		Library JSONLibrary
		Library JSONSchemaLibrary schemas/

		* Test Cases *
		POST Individual Telco-Cloud data Analytics - Method not implemented
		[Documentation] Test ID: 12.3.1.2.1
		... Test title: POST Individual Telco-Cloud data Analytics - Method not implemented
		... Test objective: The objective is to test that POST method is not implemented
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.1 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		POST Individual Telco-Cloud data Analytics
		Check HTTP Response Status Code Is 405

		GET Information about an Individual Telco-Cloud data Analytics
		[Documentation] Test ID: 12.3.1.2.2
		... Test title: GET Information about an Individual Telco-Cloud data Analytics
		... Test objective: The objective is to retrieve Information about Individual Telco-Cloud data Analytics
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		GET Individual Telco-Cloud data Analytics
		Check HTTP Response Status Code Is 200
		Check HTTP Response Body Json Schema Is individualTelcoCloudAnalytics

		GET Individual Telco-Cloud data Analytics - Not Found
		[Documentation] Test ID: 12.3.1.2.3
		... Test title: GET Individual Telco-Cloud data Analytics - Not Found
		... Test objective: The objective is to test the retrieval of information about an "Individual Telco-Cloud data Analytics" resource fails when the resource is not present.
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: Config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		Get Individual Telco-Cloud data Analytics - Not Found
		Check HTTP Response Status Code Is 404
		Check HTTP Response Body Json Schema Is ProblemDetails

		GET Information about an Individual Telco-Cloud data Analytics with permitted authorization scope
		[Documentation] Test ID: 12.3.1.2.4
		... Test title: GET Information about an Individual Telco-Cloud data Analytics with permitted authorization scope
		... Test objective: The objective is to GET Information about an Individual Telco-Cloud data Analytics with permitted authorization scope
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		GET Individual Telco-Cloud data Analytics with permitted authorization scope
		Check HTTP Response Status Code Is 201
		Check HTTP Response Body Json Schema Is individualTelcoCloudAnalytics
		GET Information about an Individual Telco-Cloud data Analytics with not permitted authorization scope
		[Documentation] Test ID: 12.3.1.2.5
		... Test title: GET Information about an Individual Telco-Cloud data Analytics with not permitted authorization scope
		... Test objective: The objective is to GET Information about an Individual Telco-Cloud data Analytics with not permitted authorization scope
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		GET Individual Telco-Cloud data Analytics with not permitted authorization scope
		Check HTTP Response Status Code Is 403
		Check HTTP Response Body Json Schema Is ProblemDetails

		GET Information about an Individual Telco-Cloud data Analytics - Unauthorized
		[Documentation] Test ID: 12.3.1.2.6
		... Test title: GET Information about an Individual Telco-Cloud data Analytics without authorization
		... Test objective: The objective is to GET Information about an Individual Telco-Cloud data Analytics without authprization
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.2 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		GET Individual Telco-Cloud data Analytics - Unauthorized
		Check HTTP Response Status Code Is 401
		Check HTTP Response Body Json Schema Is ProblemDetails

		PUT Individual Telco-Cloud data Analytics - Method not implemented
		[Documentation] Test ID: 12.3.1.2.7
		... Test title: PUT Individual Telco-Cloud data Analytics - Method not implemented
		... Test objective: The objective is to test that PUT method is not implemented
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.3 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		PUT Individual Telco-Cloud data Analytics
		Check HTTP Response Status Code Is 405

		PATCH Individual Telco-Cloud data Analytics
		[Documentation] Test ID: 12.3.1.2.8
		... Test title: PATCH Individual Telco-Cloud data Analytics
		... Test objective: This method modifies an Individual Telco-Cloud data Analytics
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: Telco-Cloud data Analytics modified
		PATCH Individual Telco-Cloud data Analytics
		Check HTTP Response Status Code Is 202
		Check HTTP Response Body Json Schema Is telcoCloudAnalyticsModifications

		PATCH Individual Telco-Cloud data Analytics - UNPROCESSABLE CONTENT
		[Documentation] Test ID: 12.3.1.2.9
		... Test title: PATCH Individual Telco-Cloud data Analytics - UNPROCESSABLE CONTENT
		... Test objective: This method modifies an Individual Telco-Cloud data Analytics with invalid content
		... Pre-conditions: none
		... Reference: Clause 5.5.4.3.4 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: none
		Patch Create a new data analytics - Unprocessable Content
		Check HTTP Response Status Code Is 422
		Check HTTP Response Body Json Schema Is ProblemDetails

		DELETE Individual Telco-Cloud data Analytics
		[Documentation] Test ID: 12.3.1.2.10
		... Test title: DELETE Individual Telco-Cloud data Analytics
		... Test objective: The objective is to delete a Telco-Cloud data Analytics
		... Pre-conditions: none
		... Reference: Clause 5.4.3.3.5 - ETSI GS NFV-SOL 025 [12] v5.2.1
		... Config ID: config_prod_NFV-MANO
		... Applicability: none
		... Post-Conditions: Telco-Cloud data Analytics deleted
		DELETE Individual Telco-Cloud data Analytics
		Check HTTP Response Status Code Is 204

SOL025/TelcoCloudDataAnalyticsService-API/jsons/telcoCloudAnalyticsModifications.json

0 → 100644

+10 −0

Original line number	Diff line number	Diff line
		{{
		"analyticsCollectionInterval": {
		"startTime": "date-time"
		},
		"locationAreaInfo": [
		{
		"countryCode" : "String"
		}
		]
		}}
		No newline at end of file

SOL025/TelcoCloudDataAnalyticsService-API/jsons/telcoCloudAnalyticsModificationsEmpty.json

0 → 100644

+3 −0

Original line number	Diff line number	Diff line
		{{

		}}
		No newline at end of file

SOL025/TelcoCloudDataAnalyticsService-API/schemas/telcoCloudAnalyticsModifications.schema.json

0 → 100644

+119 −0

Original line number	Diff line number	Diff line
		{
		"description": "This type represents modifications to a Telco-cloud data analytics. NOTE: At least one of the attributes defined in this type shall be present in request bodies. \n",
		"type": "object",
		"anyOf": [
		{
		"required": [
		"analyticsCollectionInterval"
		]
		},
		{
		"required": [
		"locationAreaInfo"
		]
		}
		],
		"properties": {
		"analyticsCollectionInterval": {
		"description": "This type represents the time interval of Telco-cloud data to be used in the Telco-cloud data analytics process.\nNOTE: When only the startTime is present, there is no time interval being defined, \n and therefore the provided timing information refers to a specific point in time \n to start the analytics.\n",
		"type": "object",
		"required": [
		"startTime"
		],
		"properties": {
		"startTime": {
		"description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
		"format": "date-time"
		},
		"endTime": {
		"description": "Date-time stamp. Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.\n",
		"format": "date-time"
		}
		}
		},
		"locationAreaInfo": {
		"description": "New values of the \"locationAreaInfo\" attribute. See note\n",
		"type": "array",
		"items": {
		"description": "This type represents the location information from which available management data is to be involved in a Telco-cloud data analytics process.\nNOTE: If both \"countryCode\" and \"area\" are present, no conflicts should exist\n between the values of these two attributes. In case of conflicts, the API\n producer (i.e. Telco-cloud DAF) shall disregard parts of the geographic\n area signalled by \"area\" that are outside the boundaries of the country\n signalled by \"countryCode\". If \"countryCode\" is absent, it is solely the\n \"area\" attribute that defines the location constraint.\n",
		"type": "object",
		"properties": {
		"countryCode": {
		"description": "The two-letter ISO 3166 country code in capital letters. Shall be present in case the \"area\" attribute is absent. May be absent if the \"area\" attribute is present (see note).\n",
		"type": "string"
		},
		"civicAddressElements": {
		"description": "Zero or more elements comprising the civic address. Shall be absent if the \"area\" attribute is present.\n",
		"type": "array",
		"items": {
		"type": "object",
		"required": [
		"caType",
		"caValue"
		],
		"properties": {
		"caType": {
		"description": "Describe the content type of caValue. The value of caType shall comply with section 3.4 of IETF RFC 4776.\n",
		"type": "integer"
		},
		"caValue": {
		"description": "Content of civic address element corresponding to the caType. The format caValue shall comply with section 3.4 of IETF RFC 4776.\n",
		"type": "string"
		}
		}
		}
		},
		"area": {
		"description": "GeoJSon geometry. See IETF RFC 7946.\n",
		"type": "object",
		"required": [
		"coordinates"
		],
		"properties": {
		"coordinates": {
		"type": "array",
		"items": {
		"description": "A linear ring is a closed LineString with four or more positions. The first and last positions are equivalent, and they MUST contain identical values; their representation SHOULD also be identical. A linear ring is the boundary of a surface or the boundary of a hole in a surface. A linear ring MUST follow the right-hand rule with respect to the area it bounds, i.e., exterior rings are counterclockwise, and holes are clockwise.\n",
		"type": "array",
		"minItems": 4,
		"items": {
		"description": "GeoJSon fundamental geometry construct. A position is an array of numbers. There MUST be two or more elements. The first two elements are longitude and latitude, or easting and northing, precisely in that order and using decimal numbers. Altitude or elevation MAY be included as an optional third element. Implementations SHOULD NOT extend positions beyond three elements because the semantics of extra elements are unspecified and ambiguous. Historically, some implementations have used a fourth element to carry a linear referencing measure (sometimes denoted as \"M\") or a numerical timestamp, but in most situations a parser will not be able to properly interpret these values. The interpretation and meaning of additional elements is beyond the scope of this specification, and additional elements MAY be ignored by parsers.\n",
		"type": "array",
		"minItems": 2,
		"maxItems": 3,
		"items": {
		"type": "number"
		}
		}
		}
		}
		}
		},
		"resourceZoneIds": {
		"description": "Identifies the resource zone(s) is to be involved in a Telco-cloud data analytics process\n",
		"type": "array",
		"items": {
		"description": "An identifier with the intention of being globally unique\n",
		"type": "string"
		}
		},
		"cisClusterIds": {
		"description": "Identifies the CIS cluster(s) is to be involved in a Telco-cloud data analytics process\n",
		"type": "array",
		"items": {
		"description": "An identifier with the intention of being globally unique\n",
		"type": "string"
		}
		},
		"containerNamespaces": {
		"description": "Identifies the container namespace(s) is to be involved in a Telco-cloud data analytics process\n",
		"type": "array",
		"items": {
		"type": "string"
		}
		}
		}
		}
		}
		}
		}
		No newline at end of file