Commit f31c606f authored by sinatra's avatar sinatra
Browse files

Merge branch 'feature/refactoring' into 'master'

Feature/refactoring

See merge request stf/stf-557/api-tests!14
parents 0c160219 b5c6c9a4
Loading
Loading
Loading
Loading
+5 −5
Original line number Diff line number Diff line
@@ -24,7 +24,7 @@ Instantiate a vnfInstance
    Check Operation Occurrence Id

Instantiate a vnfInstance Conflict
    [Documentation]    Test ID: 7.3.1.3.2
    [Documentation]    Test ID: 6.3.5.3.2
    ...    Test title: Post Instantiate Individual VNFInstance 
    ...    Test objective: The objective is to verify that the instantiation of the vnf cannot be executed currently, due to a conflict with the state of the VNF instance resource. 
    ...    Pre-conditions: VNF instance resource is in INSTANTIATED state
@@ -37,7 +37,7 @@ Instantiate a vnfInstance Conflict
    Check HTTP Response Body Json Schema Is    ProblemDetails 
    
GET Instantiate VNFInstance - Method not implemented
    [Documentation]    Test ID: 7.3.1.3.3
    [Documentation]    Test ID: 6.3.5.3.3
    ...    Test title: GET Instantiate Individual VNFInstance - Method not implemented
    ...    Test objective: The objective is to test that GET method is not implemented
    ...    Pre-conditions:  
@@ -49,7 +49,7 @@ GET Instantiate VNFInstance - Method not implemented
    Check HTTP Response Status Code Is    405
    
PUT Instantiate VNFInstance - Method not implemented
    [Documentation]    Test ID: 7.3.1.3.4
    [Documentation]    Test ID: 6.3.5.3.4
    ...    Test title: PUT Instantiate Individual VNFInstance  - Method not implemented
    ...    Test objective: The objective is to test that PUT method is not implemented
    ...    Pre-conditions:  
@@ -61,7 +61,7 @@ PUT Instantiate VNFInstance - Method not implemented
    Check HTTP Response Status Code Is    405

PATCH Instantiate VNFInstance - Method not implemented
    [Documentation]    Test ID: 7.3.1.3.5
    [Documentation]    Test ID: 6.3.5.3.5
    ...    Test title: PATCH Instantiate Individual VNFInstance  - Method not implemented
    ...    Test objective: The objective is to test that PATCH method is not implemented
    ...    Pre-conditions:  
@@ -73,7 +73,7 @@ PATCH Instantiate VNFInstance - Method not implemented
    Check HTTP Response Status Code Is    405
    
DELETE Instantiate VNFInstance - Method not implemented
     [Documentation]    Test ID: 7.3.1.3.6
     [Documentation]    Test ID: 6.3.5.3.6
    ...    Test title: DELETE Instantiate Individual VNFInstance  - Method not implemented
    ...    Test objective: The objective is to test that DELETE method is not implemented
    ...    Pre-conditions:  
+4 −4
Original line number Diff line number Diff line
@@ -17,8 +17,8 @@ Suite Teardown Terminate All Processes kill=true
*** Test Cases ***
Cancel a VNF LCM Operation - STARTING
    [Documentation]    Test ID: 7.3.1.25 
    ...    Test title: Cancel a VNF LCM Operation
    ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation
    ...    Test title: Cancel a VNF LCM Operation - STARTING
    ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation being in the STARTING state
    ...    Pre-conditions: The VNF lifecycle management operation occurrence is in STARTING state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)
    ...    Reference: section 5.4.17 - SOL003 v2.4.1
    ...    Config ID: Config_prod_VNFM
@@ -33,8 +33,8 @@ Cancel a VNF LCM Operation - STARTING

Cancel a VNF LCM Operation - PROCESSING - ROLLING_BACK
    [Documentation]    Test ID: 7.3.1.26
    ...    Test title: Cancel a VNF LCM Operation
    ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation
    ...    Test title: Cancel a VNF LCM Operation - PROCESSING - ROLLING_BACK
    ...    Test objective: The objective is to test the workflow for Cancelling a VNF LCM Operation being either in the PROCESSIONG or ROLLING_BACK state
    ...    Pre-conditions: The VNF lifecycle management operation occurrence is in PROCESSING or ROLLING_BACK state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)
    ...    Reference: section 5.3.10 - SOL003 v2.4.1
    ...    Config ID: Config_prod_VNFM
+1 −2
Original line number Diff line number Diff line
@@ -22,14 +22,13 @@ Operate a VNF Instance
    ...    Pre-conditions: VNF instance in INSTANTIATED state 
    ...    Reference: section 5.4.11 - SOL003 v2.4.1
    ...    Config ID: Config_prod_VNFM
    ...    Applicability: NFVO is able to receive notifications from VNFM. Change the external connectivity of a VNF instance is supported for the VNF (as capability in the VNFD)
    ...    Applicability: NFVO is able to receive notifications from VNFM. The VNFD supports the external connectivity change
    ...    Post-Conditions: VNF instance still in INSTANTIATED state and external connectivity of the VNF is changed
    Send Change Ext Connectivity Request
    Check HTTP Response Status Code Is    202
    Check HTTP Response Header Contains    Location 
    Check Operation Occurrence Id
    Check Operation Notification For Change Ext Connectivity    STARTING
    #Create a new Grant - Sync - OPERATE
    Check Operation Notification For Change Ext Connectivity    PROCESSING
    Check Operation Notification For Change Ext Connectivity    COMPLETED
    Check Postcondition VNF Change Ext Connectivity
+2 −2
Original line number Diff line number Diff line
@@ -15,11 +15,11 @@ Suite Teardown Terminate All Processes kill=true


*** Test Cases ***
Change VNF External Connectivity
Change VNF Flavour Workflow
    [Documentation]    Test ID: 7.3.1.28
    ...    Test title: Change VNF Flavour Workflow
    ...    Test objective: The objective is to test the workflow for a change flavour of an existing VNF instance
    ...    Pre-conditions: VNF instance in INSTANTIATED state (Test ID: 5.4.4.1). NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)
    ...    Pre-conditions: VNF instance in INSTANTIATED state . NFVO is subscribed to VNF LCM Operation Occurrence notifications 
    ...    Reference: section 5.4.7 - SOL003 v2.4.1
    ...    Config ID: Config_prod_VNFM
    ...    Applicability: Multiple flavours are supported for the VNF (as capability in the VNFD). NFVO is able to receive notifications from VNFM
+4 −3
Original line number Diff line number Diff line
@@ -15,11 +15,11 @@ Suite Teardown Terminate All Processes kill=true


*** Test Cases ***
Fail VNF LCM Operation
Fail a VNF LCM Operation Workflow
    [Documentation]    Test ID: 7.3.1.22
    ...    Test title: Fail a VNF LCM Operation
    ...    Test title: Fail a VNF LCM Operation Workflow
    ...    Test objective: The objective is to test the workflow for a Fail VNF LCM Operation
    ...    Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications (Test ID: 5.4.20.1)
    ...    Pre-conditions: The VNF lifecycle management operation occurrence is in FAILED_TEMP state. NFVO is subscribed to VNF LCM Operation Occurrence notifications 
    ...    Reference: section 5.4.16 - SOL003 v2.4.1
    ...    Config ID: Config_prod_VNFM
    ...    Applicability: NFVO is able to receive notifications from VNFM
@@ -48,3 +48,4 @@ Check Operation Notification For Fail
    [Arguments]    ${status}
    Check Operation Notification    VnfLcmOperationOccurrenceNotification   ${status}
    
    
 No newline at end of file
Loading