Commit 3de4c42a authored by Muhammad Hamza's avatar Muhammad Hamza Committed by Giacomo Bernini
Browse files

Add 403 Forbidden Testcase, Add variables.txt file

parent 83a08017

SOL002/VNFLCMCoordination-API/Coordinations.robot

+21 −9
Original line number Original line Diff line number Diff line
@@ -42,8 +42,8 @@ POST Coordination of LCM Operation Occurance and API Producer has Chosen the Asy 
POST Coordination of a LCM Operation Occurance Forbidden

POST Coordination of a LCM Operation Occurance Forbidden

    [Documentation]    Test ID: 6.3.6.2.3

    [Documentation]    Test ID: 6.3.6.2.3

    ...    Test title: Post Coordination of an LCM operation occurrence Forbidden

    ...    Test title: Post Coordination of an LCM operation occurrence Forbidden

    ...    Test Objective: The objective is to verify that the coordination of LCM operation occurance has been rejected.

    ...    Test Objective: The objective is to test the failure of a request for the coordination of an LCM operation occurrence

    ...    pre-condition: LCM operation occurrence resource is in Processing state

    ...    pre-condition: The status of the related LCM opeation occurrence is "PROCESSING". The request is performed by a user that has not the grant to run this operation

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Config ID: Config_prod_VE

    ...    Config ID: Config_prod_VE

    ...    Applicability: none  

    ...    Applicability: none
@@ -56,7 +56,7 @@ POST Coordination of LCM Operation Occurance Conflict 
    [Documentation]    Test ID: 6.3.6.2.4

    [Documentation]    Test ID: 6.3.6.2.4

    ...    Test title: Post Coordination of an LCM operation occurrence Conflict

    ...    Test title: Post Coordination of an LCM operation occurrence Conflict

    ...    Test Objective: The objective is to verify that no coordination actions can be executed currently, due to a conflict with the state of the "Coordinations" resource.

    ...    Test Objective: The objective is to verify that no coordination actions can be executed currently, due to a conflict with the state of the "Coordinations" resource.

    ...    pre-condition: LCM operation occurrence resource is in Processing state

    ...    pre-condition: The status of the related LCM opeation occurrence is not "PROCESSING"

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Config ID: Config_prod_VE

    ...    Config ID: Config_prod_VE

    ...    Applicability: When there are many coordination actions exist, or conflicting ones, are in progress.

    ...    Applicability: When there are many coordination actions exist, or conflicting ones, are in progress.
@@ -68,8 +68,8 @@ POST Coordination of LCM Operation Occurance Conflict 
POST Coordination of LCM Operation Occurance Service Unavailable 

POST Coordination of LCM Operation Occurance Service Unavailable 

    [Documentation]    Test ID: 6.3.6.2.5

    [Documentation]    Test ID: 6.3.6.2.5

    ...    Test title: Post Coordination of an LCM operation occurrence Service Unavailable 

    ...    Test title: Post Coordination of an LCM operation occurrence Service Unavailable 

    ...    Test Objective: The objective is to verify that requested coordination operation cannot be executed currently. 

    ...    Test Objective: The objective is to test the request for the coordination of an LCM operation occurrence and the verify that the NFVO cannot perform immediately the request, but can perform it sometime in the future. 

    ...    pre-condition: LCM operation occurrence resource is in Processing state

    ...    pre-condition: The status of the related LCM opeation occurrence is "PROCESSING" but API producer cannot perform immediately the request

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Config ID: Config_prod_VE

    ...    Config ID: Config_prod_VE

    ...    Applicability: API producer has chosen the synchronous mode

    ...    Applicability: API producer has chosen the synchronous mode
@@ -79,8 +79,20 @@ POST Coordination of LCM Operation Occurance Service Unavailable 
    Check HTTP Response Header Contains    Retry-After

    Check HTTP Response Header Contains    Retry-After

    Check HTTP Response Body Json Schema Is    ProblemDetails

    Check HTTP Response Body Json Schema Is    ProblemDetails





GET Coordination of a LCM Operation Occurance - Method not implemented

POST Coordination of an LCM operation occurrence without authentication

    [Documentation]    Test ID: 6.3.6.2.6

    [Documentation]    Test ID: 6.3.6.2.6

    ...    Test title:  Request a Coordination of an LCM operation occurrence without authentication

    ...    Test objective: The objective is to test the failure of the request for the coordination of an LCM operation occurrence without providing an authentication token

    ...    Pre-conditions: The status of the related LCM opeation occurrence is "PROCESSING"

    ...    Reference: Clause 10.4.2.3.1 - ETSI GS NFV-SOL 002 [2] v3.5.1

    ...    Config ID: Config_prod_VE

    ...    Applicability: none

    ...    Post-Conditions: none

    Post Request for coordination of an LCM operation occurrence without authorization token

    Check HTTP Response Status Code Is    401



GET Coordination of a LCM Operation Occurance - Method not implemented

    [Documentation]    Test ID: 6.3.6.2.7

    ...    Test title: GET Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test title: GET Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test Objective: The objective is to test that GET method for Resource Coordinations is not implemented.

    ...    Test Objective: The objective is to test that GET method for Resource Coordinations is not implemented.

    ...    pre-condition: none

    ...    pre-condition: none
@@ -92,7 +104,7 @@ GET Coordination of a LCM Operation Occurance - Method not implemented 
    Check HTTP Response Status Code Is    405

    Check HTTP Response Status Code Is    405





PUT Coordination of a LCM Operation Occurance - Method not implemented

PUT Coordination of a LCM Operation Occurance - Method not implemented

    [Documentation]    Test ID: 6.3.6.2.7

    [Documentation]    Test ID: 6.3.6.2.8

    ...    Test title: PUT Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test title: PUT Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test Objective: The objective is to test that PUT method for Resource Coordinations is not implemented.

    ...    Test Objective: The objective is to test that PUT method for Resource Coordinations is not implemented.

    ...    pre-condition: none

    ...    pre-condition: none
@@ -104,7 +116,7 @@ PUT Coordination of a LCM Operation Occurance - Method not implemented 
    Check HTTP Response Status Code Is    405

    Check HTTP Response Status Code Is    405





PACTH Coordination of a LCM Operation Occurance - Method not implemented

PACTH Coordination of a LCM Operation Occurance - Method not implemented

    [Documentation]    Test ID: 6.3.6.2.8

    [Documentation]    Test ID: 6.3.6.2.9

    ...    Test title: PATCH Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test title: PATCH Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test Objective: The objective is to test that PATCH method for Resource Coordinations is not implemented.

    ...    Test Objective: The objective is to test that PATCH method for Resource Coordinations is not implemented.

    ...    pre-condition: none

    ...    pre-condition: none
@@ -116,7 +128,7 @@ PACTH Coordination of a LCM Operation Occurance - Method not implemented 
    Check HTTP Response Status Code Is    405

    Check HTTP Response Status Code Is    405





DELETE Coordination of a LCM Operation Occurance - Method not implemented

DELETE Coordination of a LCM Operation Occurance - Method not implemented

    [Documentation]    Test ID: 6.3.6.2.9

    [Documentation]    Test ID: 6.3.6.2.10

    ...    Test title: DELETE Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test title: DELETE Coordination of a LCM Operation Occurance - Method not implemented

    ...    Test Objective: The objective is to test that DELETE method for Resource Coordinations is not implemented.

    ...    Test Objective: The objective is to test that DELETE method for Resource Coordinations is not implemented.

    ...    pre-condition: none

    ...    pre-condition: none

SOL002/VNFLCMCoordination-API/VNFLCMCoordinationKeywords.robot

+68 −59

File changed.

Preview size limit exceeded, changes collapsed.

SOL002/VNFLCMCoordination-API/environment/variables.txt

+3 −2
Original line number Original line Diff line number Diff line
@@ -2,6 +2,7 @@ 
${AUTH_USAGE}      1

${AUTH_USAGE}      1

${AUTHORIZATION_HEADER}      Authorization

${AUTHORIZATION_HEADER}      Authorization

${AUTHORIZATION_TOKEN}      Bearer 0b79bab50daca910b000d4f1a2b675d604257e42

${AUTHORIZATION_TOKEN}      Bearer 0b79bab50daca910b000d4f1a2b675d604257e42

${INSUFFICIENT_AUTHORIZATION_TOKEN}    Bearer INSUFFICIENT_AUTHORIZATION_TOKEN  #The provided authorization token can be insufficient, expired, etc, and server refuses to authorize the request with this token.

${apiRoot}      /

${apiRoot}      /

${apiName}      lcmcoord

${apiName}      lcmcoord

${apiMajorVersion}      v1

${apiMajorVersion}      v1
@@ -9,8 +10,8 @@ ${response}= httpresponse 
${EM-VNF_HOST}      localhost    # Hostname of the NFVO

${EM-VNF_HOST}      localhost    # Hostname of the NFVO

${EM-VNF_PORT}      8081    # Listening port of the NFVO

${EM-VNF_PORT}      8081    # Listening port of the NFVO

${EM-VNF_SCHEMA}    https

${EM-VNF_SCHEMA}    https

${CONTENT_TYPE}    application/json

${CONTENT_TYPE_JSON}    application/json

${ACCEPT}         application/json

${ACCEPT_JSON}         application/json





${SYNCHRONOUS_MODE_SUPPORT}      1  #Set it to 0 if API producer supporting Asynchronous mode, and set it to 1 if API producer supporting Synchronous mode.

${SYNCHRONOUS_MODE_SUPPORT}      1  #Set it to 0 if API producer supporting Asynchronous mode, and set it to 1 if API producer supporting Synchronous mode.