Skip to content
GitLab
Commit a9278c20 authored by Elian Kraja's avatar Elian Kraja
Browse files

Fixing typos

parent d693824f
Hide whitespace changes
Inline Side-by-side
SOL003/VNFLifecycleManagement-API/CancelOperationTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/ChangeExternalVNFConnectivityTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/ChangeVNFFlavourTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/FailOperationTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/HealVNFTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/IndividualSubscription.robot
View file @ a9278c20
......@@ -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
......
SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/InstantiateVNFTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/OperateVNFTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/RetryOperationTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/RollbackOperationTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/ScaleVNFTaskWorkflow.robot
View file @ a9278c20
......@@ -7,7 +7,7 @@ Library OperatingSystem
Library BuiltIn
Library Collections
Library JSONLibrary
*** Test Cases ***
Precondition Checks
......
SOL003/VNFLifecycleManagement-API/ScaleVNFToLevelTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/TerminateVNFTask.robot
View file @ a9278c20
......@@ -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}"}
......
SOL003/VNFLifecycleManagement-API/VNFInstances.robot
View file @ a9278c20
......@@ -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
......
SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
View file @ a9278c20
......@@ -5,10 +5,8 @@ Library OperatingSystem
Library BuiltIn
Library JSONLibrary
Library JSONSchemaLibrary schemas/
*** Keywords ***
Get Vnf Instance
[Arguments] ${vnfInstanceId}
Set Headers {"Accept":"${ACCEPT}"}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment