minor bug fixes and an additional test for filter based quering of VNFSnapshotPackages resource

GET Information about an individual VNF Snapshot Package - SUCCESSFUL

    [Documentation]    Test ID: 7.3.8.3.2

    ...    Test title: GET Information about an individual VNF Snapshot Package - SUCCESSFUL

    ...    Test objective: The objective is to create a new VNF Snapshot Package resource

    ...    Test objective: The objective is to query information about a VNF Snapshot Package resource

    ...    Pre-conditions: none

    ...    Reference: Clause 12.4.3.3.2 - ETSI GS NFV-SOL 003 [1] v3.3.1

    ...    Config ID: Config_prod_NFVO

    ...    Post-Conditions: VNF snapshot package is not deleted

    DELETE VNF Snapshot Packages

    Check HTTP Response Status Code Is    405

GET information about multiple VNF Snapshot Packages using filter

    [Documentation]    Test ID: 7.3.8.2.15

    ...    Test title: GET information about multiple VNF Snapshot Packages using filter

    ...    Test objective: The objective is to get information about multiples VNF Snapshot Packages using filter

    ...    Pre-conditions: none

    ...    Reference: Clause 12.4.2.3.2 - ETSI GS NFV-SOL 003 [1] v3.3.1

    ...    Config ID: Config_prod_NFVO

    ...    Applicability: none

    ...    Post-Conditions: none

    GET multiple VNF Snapshot Packages using filter

    Check HTTP Response Status Code Is    200

    Check HTTP Response Body Json Schema Is    VnfSnapshotPkgInfos

    Set Headers  {"Accept":"${ACCEPT_JSON}"}  

    Set Headers  {"Content-Type": "${CONTENT_TYPE_JSON}"}

    Run Keyword If    ${AUTH_USAGE} == 1    Set Headers    {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"} 

    GET    ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshot_packages?fields=wrong_field

    GET    ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshot_packages?${NEG_FILTER}

    ${outputResponse}=    Output    response

	Set Global Variable    ${response}    ${outputResponse} 	

GET multiple VNF Snapshot Packages using filter	

    Log    Query VNF The GET method queries information about multiple VNF Snapshot Packages.

    Set Headers  {"Accept":"${ACCEPT_JSON}"}  

    Set Headers  {"Content-Type": "${CONTENT_TYPE_JSON}"}

    Run Keyword If    ${AUTH_USAGE} == 1    Set Headers    {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"} 

    GET    ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshot_packages?${POS_FILTER}

    ${outputResponse}=    Output    response

	Set Global Variable    ${response}    ${outputResponse} 	

    Log    Query status information about multiple VNF Snapshot Packages, using fields

    Set Headers    {"Accept": "${ACCEPT_JSON}"}

    Run Keyword If    ${AUTH_USAGE} == 1    Set Headers    {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}

    GET    ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshot_packages?exclude_default

    GET    ${apiRoot}/${apiName}/${apiMajorVersion}/vnf_snapshot_packages?all_fields

    ${output}=    Output    response

    Set Suite Variable    ${response}    ${output}

${length}          1024

${POS_FILTER}     vnfdId=41fdd38a-3d4c-465c-83e0-f80e014425f8 ,vnfProvider=NXW    # Positive case, suing compiant fields name for filtering get request

${POS_FILTER}     id=41fdd38a-3d4c-465c-83e0-f80e014425f8 ,vnfProvider=NXW    # Positive case, suing compiant fields name for filtering get request

${NEG_FILTER}     nfvId=41fdd38a-3d4c-465c-83e0-f80e014425f8    # Negative case, using wrong name of field

${fields}         softwareImages,additionalArtifacts

${VAR_SEPERATOR}    &

{  "description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced inthis structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",  "type": "object",  "required": [    "status",    "detail"  ],  "properties": {    "type": {      "description": "A URI reference according to IETF RFC 3986 [5] that identifies the problem type. It is encouraged that the URI provides human-readable documentation for the problem (e.g. using HTML) when dereferenced. When this member is not present, its value is assumed to be \"about:blank\".\n",      "type": "string",      "format": "URI"    },    "title": {      "description": "A short, human-readable summary of the problem type. It should not change from occurrence to occurrence of the problem, except for purposes of localization. If type is given and other than \"about:blank\", this attribute shall also be provided. A short, human-readable summary of the problem type.  It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization (e.g., using proactive content negotiation; see [RFC7231], Section 3.4).\n",      "type": "string"    },    "status": {      "description": "The HTTP status code for this occurrence of the problem. The HTTP status code ([RFC7231], Section 6) generated by the origin server for this occurrence of the problem.\n",      "type": "integer"    },    "detail": {      "description": "A human-readable explanation specific to this occurrence of the problem.\n",      "type": "string"    },    "instance": {      "description": "A URI reference that identifies the specific occurrence of the problem. It may yield further information if dereferenced.\n",      "type": "string",      "format": "URI"    }  }}

 No newline at end of file