From a9278c207cabde9a139d9777d0af215c2278c447 Mon Sep 17 00:00:00 2001 From: Elian Kraja Date: Tue, 8 Jan 2019 17:37:32 +0100 Subject: [PATCH] Fixing typos --- .../CancelOperationTask.robot | 8 ++++---- .../ChangeExternalVNFConnectivityTask.robot | 4 ++-- .../ChangeVNFFlavourTask.robot | 8 ++++---- .../VNFLifecycleManagement-API/FailOperationTask.robot | 8 ++++---- SOL003/VNFLifecycleManagement-API/HealVNFTask.robot | 8 ++++---- .../IndividualSubscription.robot | 2 +- .../IndividualVNFInstance.robot | 8 ++++---- .../InstantiateVNFTask.robot | 4 ++-- SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot | 8 ++++---- .../RetryOperationTask.robot | 8 ++++---- .../RollbackOperationTask.robot | 10 +++++----- SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot | 8 ++++---- .../ScaleVNFTaskWorkflow.robot | 2 +- .../ScaleVNFToLevelTask.robot | 8 ++++---- .../VNFLifecycleManagement-API/TerminateVNFTask.robot | 6 +++--- SOL003/VNFLifecycleManagement-API/VNFInstances.robot | 3 +-- .../VnfLcmMntOperationKeywords.robot | 2 -- 17 files changed, 51 insertions(+), 54 deletions(-) diff --git a/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot b/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot index eb4818f2..c434253c 100644 --- a/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot +++ b/SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot @@ -6,7 +6,7 @@ Library DependencyLibrary Library JSONLibrary Library JSONSchemaLibrary schemas/ Documentation This task resource represents the "Cancel operation" operation. The client can use this resource to cancel an ongoing VNF lifecycle operation. -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Post Cancel operation task @@ -28,7 +28,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or rollback. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. Depends on test failure Check resource FAILED_TEMP Log Final Fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -46,7 +46,7 @@ Post Fail operation task Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or rollback. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another error handling action log Final Fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -66,7 +66,7 @@ Post Fail operation task Not Found ... Specifically in case of this task resource, the response code 404 shall also be returned ... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource, ... which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check Fail not supported log Final fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} diff --git a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot index 0de5acd1..dbf8f8f2 100644 --- a/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot +++ b/SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Change external VNF connectivity @@ -27,7 +27,7 @@ Change external VNF connectivity Conflict (parallel LCM operation) [Documentation] Conflict ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that another LCM operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to change the deployment flavour of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot index c0843b6c..2619eefe 100644 --- a/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot +++ b/SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Change deployment flavour of a vnfInstance @@ -28,7 +28,7 @@ Change deployment flavour of a vnfInstance Conflict (Not-Instantiated) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to change the deployment flavour of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -49,7 +49,7 @@ Change deployment flavour of a vnfInstance Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to change the deployment flavour of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -70,7 +70,7 @@ Change deployment flavour of a vnfInstance Not Found [Documentation] Not Found ... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. ... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check change flavour not supported Log Trying to change the deployment flavour of a VNF instance, not exist Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot b/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot index 263c223a..7ea57b36 100644 --- a/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot +++ b/SOL003/VNFLifecycleManagement-API/FailOperationTask.robot @@ -9,7 +9,7 @@ Documentation This task resource represents the "Fail operation" operation. ... The client can use this resource to mark a VNF lifecycle management operation occurrence as "finally failed", ... i.e. change the state of the related VNF LCM operation occurrence resource to "FAILED", if it is not assumed that a subsequent retry or rollback will succeed. ... Once the operation is marked as "finally failed", it cannot be retried or rolled back anymore. -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Post Fail operation task @@ -31,7 +31,7 @@ Post Fail operation task Conflict (Not-FAILED_TEMP) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or rollback. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. Depends on test failure Check resource FAILED_TEMP Log Final Fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -49,7 +49,7 @@ Post Fail operation task Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or rollback. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another error handling action log Final Fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -69,7 +69,7 @@ Post Fail operation task Not Found ... Specifically in case of this task resource, the response code 404 shall also be returned ... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource, ... which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check Fail not supported log Final fail an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} diff --git a/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot b/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot index 0b4b2ed7..dfbd12cc 100644 --- a/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot +++ b/SOL003/VNFLifecycleManagement-API/HealVNFTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Heal a vnfInstance @@ -28,7 +28,7 @@ Heal a vnfInstance Conflict (Not-Instantiated) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to heal a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -49,7 +49,7 @@ Heal a vnfInstance Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to heal a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -70,7 +70,7 @@ Heal a vnfInstance Not Found [Documentation] Not Found ... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. ... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check heal not supported Log Trying to heal a VNF instance, not exist Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot b/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot index b5e9c3b2..f3dc02cf 100644 --- a/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot +++ b/SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot @@ -6,7 +6,7 @@ Library JSONLibrary Library JSONSchemaLibrary schemas/ Documentation This resource represents an individual subscription. The client can use this resource to read and to terminate a ... subscription to notifications related to VNF lifecycle management -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Post Individual Subscription - Method not implemented diff --git a/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot b/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot index 5b335aca..7c3026c9 100644 --- a/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot +++ b/SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot @@ -9,7 +9,7 @@ Library JSONLibrary Library JSONSchemaLibrary schemas/ Documentation This resource represents an individual VNF instance. The client can use this resource to modify and delete the ... underlying VNF instance, and to read information about the VNF instance. -Suite setup Check resource existance +Suite Setup Check resource existance *** Variables *** ${Etag}= an etag @@ -72,7 +72,7 @@ PATCH Individual VNFInstance Precondition failed [Documentation] 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. + ... The response body should contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. Depends On Test PATCH Individual VNFInstance # If the previous test scceeded, it means that Etag has been modified log Trying to modify an individual VNF instance Precondition failed Set Headers {"Accept":"${ACCEPT}"} @@ -92,7 +92,7 @@ PATCH Individual VNFInstance Conflict # TODO: Need to set the pre-condition of the test [Documentation] Conflict ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. - ... Typically, this is due to the fact that another LCM operation is ongoing. The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... Typically, this is due to the fact that another LCM operation is ongoing. The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to modify an individual VNF instance Set Headers {"Accept":"${ACCEPT}"} @@ -122,7 +122,7 @@ DELETE Individual VNFInstance Conflict [Documentation] Conflict ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in INSTANTIATED state. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource instantiated log Trying to delete an individual VNF instance Conflict Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} diff --git a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot index c9e928fa..70be1f05 100644 --- a/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot +++ b/SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot @@ -6,7 +6,7 @@ Library DependencyLibrary Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** @@ -29,7 +29,7 @@ Instantiate a vnfInstance Conflict [Documentation] Conflict. ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in INSTANTIATED state. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource instantiated Log Trying to Instantiate a vnf Instance Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot index 6e420cac..92d34605 100644 --- a/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot +++ b/SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Operate a vnfInstance @@ -28,7 +28,7 @@ Operate a vnfInstance Conflict (Not-Instantiated) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to change the operational state of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -49,7 +49,7 @@ Operate a vnfInstance Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to change the operational state of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -70,7 +70,7 @@ Operate a vnfInstance Not Found [Documentation] Not Found ... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. ... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check operate not supported Log Trying to change the operational state of a VNF instance, not exist Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot b/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot index f7e42078..f83178e5 100644 --- a/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot +++ b/SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot @@ -6,7 +6,7 @@ Library DependencyLibrary Library JSONLibrary Library JSONSchemaLibrary schemas/ Documentation This task resource represents the "Retry operation" operation. The client can use this resource to initiate retrying a VNF lifecycle operation. -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Post Retry operation task @@ -29,7 +29,7 @@ Post Retry operation task Conflict (Not-FAILED_TEMP) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as rollback or fail. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. Depends on test failure Check resource FAILED_TEMP Log Retry an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -49,7 +49,7 @@ Post Retry operation task Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as rollback or fail. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another error handling action log Retry an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -69,7 +69,7 @@ Post Retry operation task Not Found ... Specifically in case of this task resource, the response code 404 shall also be returned ... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource, ... which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check retry not supported log Retry an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} diff --git a/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot b/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot index 62d814d0..c9c820a7 100644 --- a/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot +++ b/SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot @@ -6,12 +6,12 @@ Library DependencyLibrary Library JSONLibrary Library JSONSchemaLibrary schemas/ Documentation This task resource represents the "Rollback operation" operation. The client can use this resource to initiate rolling back a VNF lifecycle operation -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Post Rollback operation task [Documentation] The POST method initiates rolling back a VNF lifecycle operation if that operation has experienced a temporary failure, - ... i.e. the related “VNF LCM operation occurrence” resource is in “FAILED_TEMP” state. + ... i.e. the related �VNF LCM operation occurrence� resource is in �FAILED_TEMP� state. Depends on test Check resource FAILED_TEMP Log Rollback a VNF lifecycle operation if that operation has experienced a temporary failure Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -29,7 +29,7 @@ Post Rollback operation task Conflict (Not-FAILED_TEMP) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or fail. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. Depends on test failure Check resource FAILED_TEMP Log Rollback an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -48,7 +48,7 @@ Post Rollback operation task Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is not in FAILED_TEMP state, ... or another error handling action is starting, such as retry or fail. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another error handling action log Rollback an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} @@ -68,7 +68,7 @@ Post Rollback operation task Not Found ... Specifically in case of this task resource, the response code 404 shall also be returned ... if the task is not supported for the VNF LCM operation occurrence represented by the parent resource, ... which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check Rollback not supported log Rollback an operation Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization":"${AUTHORIZATION}"} diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot index fe11110b..b0999b57 100644 --- a/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot +++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Scale a vnfInstance @@ -27,7 +27,7 @@ Scale a vnfInstance Conflict (Not-Instantiated) [Documentation] Conflict. ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to Scale a vnf Instance Set Headers {"Accept":"${ACCEPT}"} @@ -47,7 +47,7 @@ Scale a vnfInstance Conflict (parallel LCM operation) [Documentation] Conflict ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to Scale a vnf Instance Set Headers {"Accept":"${ACCEPT}"} @@ -68,7 +68,7 @@ Scale a vnfInstance Not Found [Documentation] Not Found ... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. ... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check scale not supported Log Trying to scale a vnf Instance, not exist Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFTaskWorkflow.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFTaskWorkflow.robot index 679a9d1a..1737ad60 100644 --- a/SOL003/VNFLifecycleManagement-API/ScaleVNFTaskWorkflow.robot +++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFTaskWorkflow.robot @@ -7,7 +7,7 @@ Library OperatingSystem Library BuiltIn Library Collections Library JSONLibrary - + *** Test Cases *** Precondition Checks diff --git a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot index abd066a7..58c55f70 100644 --- a/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot +++ b/SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Scale a vnfInstance to level @@ -27,7 +27,7 @@ Scale a vnfInstance to level Conflict (Not-Instantiated) [Documentation] Conflict. ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to Scale a vnf Instance Set Headers {"Accept":"${ACCEPT}"} @@ -46,7 +46,7 @@ Scale a vnfInstance to level Conflict (parallel LCM operation) [Documentation] Conflict ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to Scale a vnf Instance Set Headers {"Accept":"${ACCEPT}"} @@ -67,7 +67,7 @@ Scale a vnfInstance Not Found [Documentation] Not Found ... Error: The API producer did not find a current representation for the target resource or is not willing to disclose that one exists. ... Specifically in case of this task resource, the response code 404 shall also returned if the task is not supported for the VNF instance represented by the parent resource, which means that the task resource consequently does not exist. - ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the “detail” attribute shall convey more information about the error. + ... In this case, the response body shall be present, and shall contain a ProblemDetails structure, in which the �detail� attribute shall convey more information about the error. [Setup] Check scale to level not supported Log Trying to scale a vnf Instance, not exist Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot b/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot index 44847aa2..0d905b0b 100644 --- a/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot +++ b/SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot @@ -5,7 +5,7 @@ Library REST ${VNFM_SCHEMA}://${VNFM_HOST}:${VNFM_PORT} Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -Suite setup Check resource existance +Suite Setup Check resource existance *** Test Cases *** Terminate a vnfInstance @@ -28,7 +28,7 @@ Terminate a vnfInstance Conflict (Not-Instantiated) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Check resource not instantiated Log Trying to terminate a VNF instance. Set Headers {"Accept":"${ACCEPT}"} @@ -49,7 +49,7 @@ Terminate a vnfInstance Conflict (parallel LCM operation) ... The operation cannot be executed currently, due to a conflict with the state of the VNF instance resource. ... Typically, this is due to the fact that the VNF instance resource is in NOT-INSTANTIATED state, ... or that another lifecycle management operation is ongoing. - ... The response body shall contain a ProblemDetails structure, in which the “detail” attribute should convey more information about the error. + ... The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error. [Setup] Launch another LCM operation log Trying to change the deployment flavour of a VNF instance. Set Headers {"Accept":"${ACCEPT}"} diff --git a/SOL003/VNFLifecycleManagement-API/VNFInstances.robot b/SOL003/VNFLifecycleManagement-API/VNFInstances.robot index 3eeec080..a393cfc8 100644 --- a/SOL003/VNFLifecycleManagement-API/VNFInstances.robot +++ b/SOL003/VNFLifecycleManagement-API/VNFInstances.robot @@ -7,8 +7,7 @@ Library OperatingSystem Library JSONLibrary Library JSONSchemaLibrary schemas/ -*** Test cases *** - +*** Test Cases *** Create a new vnfInstance [Setup] #make sure the vnfInstand ${vnfInstanceId} doesn't exist Log Create VNF instance by POST to ${apiRoot}/${apiName}/${apiVersion}/vnf_instances diff --git a/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot b/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot index 5bdb3be8..f625a230 100644 --- a/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot +++ b/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot @@ -5,10 +5,8 @@ Library OperatingSystem Library BuiltIn Library JSONLibrary Library JSONSchemaLibrary schemas/ - *** Keywords *** - Get Vnf Instance [Arguments] ${vnfInstanceId} Set Headers {"Accept":"${ACCEPT}"} -- GitLab