api-tests issueshttps://forge.etsi.org/rep/nfv/api-tests/-/issues2021-10-05T10:15:18Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/90[GENERIC] Content-Type when errors occur should be application/problem+json2021-10-05T10:15:18ZElian Kraja[GENERIC] Content-Type when errors occur should be application/problem+jsonAs per 4.3.5.2 General mechanism when an error occurs the Content-Type shall be set to "application/problem+json"As per 4.3.5.2 General mechanism when an error occurs the Content-Type shall be set to "application/problem+json"https://forge.etsi.org/rep/nfv/api-tests/-/issues/89Header Location shhould not be checked in Individual VNF LCM operation occurr...2021-06-03T08:49:18ZElian KrajaHeader Location shhould not be checked in Individual VNF LCM operation occurrenceIn the operations of Retry, rollback etc, on the POST method the check on Location header should be removed.In the operations of Retry, rollback etc, on the POST method the check on Location header should be removed.https://forge.etsi.org/rep/nfv/api-tests/-/issues/88Update requirements.txt is needed2019-06-27T07:23:38ZElian KrajaUpdate requirements.txt is neededLine 8: `robotframework-jsonlibrary==0.2` should become `robotframework-jsonlibrary` and the extention file for the jsonlibrary should be removed since the patch is not more necessaryLine 8: `robotframework-jsonlibrary==0.2` should become `robotframework-jsonlibrary` and the extention file for the jsonlibrary should be removed since the patch is not more necessaryElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/87Update on Subscriptions in SOL005/VNFPackageManagement-API when duplications ...2019-06-27T07:23:59ZElian KrajaUpdate on Subscriptions in SOL005/VNFPackageManagement-API when duplications are testedKeyword `Send Post Request for Duplicated VNF Package Subscription` should not check the fact that the NFVO is able or not to handle duplication of the subscriptions, since the behaviour based on the result is checked on the next steps o...Keyword `Send Post Request for Duplicated VNF Package Subscription` should not check the fact that the NFVO is able or not to handle duplication of the subscriptions, since the behaviour based on the result is checked on the next steps of the main keyword.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/86Unable to generate 404 in all operations in LCM2019-06-18T15:57:34ZElian KrajaUnable to generate 404 in all operations in LCMIn all operations (instantiate, scale, operate ...) the Test Case related to the 404 is not able to trigger that error. URI may need to change.In all operations (instantiate, scale, operate ...) the Test Case related to the 404 is not able to trigger that error. URI may need to change.https://forge.etsi.org/rep/nfv/api-tests/-/issues/85Wrong URI in SOL002/VNFIndicator-API/VNFIndicators.robot2020-10-26T06:13:39ZElian KrajaWrong URI in SOL002/VNFIndicator-API/VNFIndicators.robotLine 209 should contain a wrong URI
i.e.: `Get ${apiRoot}/${apiName}/${apiVersion}/indicator`Line 209 should contain a wrong URI
i.e.: `Get ${apiRoot}/${apiName}/${apiVersion}/indicator`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/84Keyword "Check resource instantiated" in SOL003/VNFLifeCycleManagement-API sh...2020-11-19T14:48:27ZElian KrajaKeyword "Check resource instantiated" in SOL003/VNFLifeCycleManagement-API should be parametrizedThe keyword "Check resource instantiated" checks always the same variable ${vnfInstance} even when the task is trying to use another one
I.e.: Instantiate a vnfInstance Conflict in InstantiateVNFTask.robot is trying to instantiate a vnf...The keyword "Check resource instantiated" checks always the same variable ${vnfInstance} even when the task is trying to use another one
I.e.: Instantiate a vnfInstance Conflict in InstantiateVNFTask.robot is trying to instantiate a vnf with ID ${instantiatedVnfInstanceId}, but in the SETUP part, the "Check resource instantiated" performs a check on instance id ${vnfInstance}https://forge.etsi.org/rep/nfv/api-tests/-/issues/83Missing schema in SOL003/VNFLifeCycleManagement-API2021-06-03T08:49:18ZElian KrajaMissing schema in SOL003/VNFLifeCycleManagement-APINo such file or directory: 'schemas//VnfLcmOpOcc.schema.json'No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'https://forge.etsi.org/rep/nfv/api-tests/-/issues/82ETag should not be checked on PATCH Operations2020-11-18T18:58:30ZElian KrajaETag should not be checked on PATCH OperationsIn the PATCH operations, it should be avoided the check of the ETag, since the operation will be asynchronous. In fact, a 202 Accepted is returned and as reported in the spec (Table 5.4.3.3.4-2 of SOL003):
`The request was accepted for ...In the PATCH operations, it should be avoided the check of the ETag, since the operation will be asynchronous. In fact, a 202 Accepted is returned and as reported in the spec (Table 5.4.3.3.4-2 of SOL003):
`The request was accepted for processing, but the processing has not been completed.`
FILE: SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robothttps://forge.etsi.org/rep/nfv/api-tests/-/issues/81Keyword "Check Postcondition VNF Package Subscription Is Set" should be checked2019-06-27T07:24:10ZElian KrajaKeyword "Check Postcondition VNF Package Subscription Is Set" should be checkedKEYWORD BuiltIn . Run Keyword If Should Not Be Equal As Strings, ${location}, Location, GET, ${apiRoot}/${apiName}/${apiVersion}/subscriptions/${response['body']['id']}
Runs the given keyword with the given arguments, if condition is tr...KEYWORD BuiltIn . Run Keyword If Should Not Be Equal As Strings, ${location}, Location, GET, ${apiRoot}/${apiName}/${apiVersion}/subscriptions/${response['body']['id']}
Runs the given keyword with the given arguments, if condition is true.
Start / End / Elapsed: 20190604 12:57:00.774 / 20190604 12:57:00.775 / 00:00:00.001
12:57:00.775 FAIL Evaluating expression 'Should Not Be Equal As Strings' failed: SyntaxError: invalid syntax (<string>, line 1)Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/78Error loading json in PNFContent2019-06-27T07:24:53ZElian KrajaError loading json in PNFContentIn order to correctly load jsons, should be used the `Get File` keyword instead of `Get Binary File`In order to correctly load jsons, should be used the `Get File` keyword instead of `Get Binary File`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/73BuiltIn Catenate keyword need a separator in order to avoid space between words2021-06-03T08:49:18ZElian KrajaBuiltIn Catenate keyword need a separator in order to avoid space between wordsShould become
`
${str3} = Catenate SEPARATOR= Hello world
`
* [x] v2.6.1
* [x] v2.7.1Should become
`
${str3} = Catenate SEPARATOR= Hello world
`
* [x] v2.6.1
* [x] v2.7.1Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/72Missing GET Not Found (Wrong URI) option on NSDescriptors.robot2019-09-19T13:56:55ZElian KrajaMissing GET Not Found (Wrong URI) option on NSDescriptors.robotThe check on wrong URI is missing on NSDescriptors
FILE: SOL005/NSDManagement-API/NSDescriptors.robotThe check on wrong URI is missing on NSDescriptors
FILE: SOL005/NSDManagement-API/NSDescriptors.robotGiacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/71Wrong variable on Scale a vnfInstance Conflict (Not-Instantiated)2021-06-03T08:49:18ZElian KrajaWrong variable on Scale a vnfInstance Conflict (Not-Instantiated)The POST action on line 36
Post ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale ${body}
should use a vnfInstanceId which is in "NOT_INSTANTIATED" operationalState.
Name should change accordingly
FILE: SOL...The POST action on line 36
Post ${apiRoot}/${apiName}/${apiVersion}/vnf_instances/${vnfInstanceId}/scale ${body}
should use a vnfInstanceId which is in "NOT_INSTANTIATED" operationalState.
Name should change accordingly
FILE: SOL002/VNFLifecycleManagement-API/ScaleVNFTask.robothttps://forge.etsi.org/rep/nfv/api-tests/-/issues/70Wrong SETUP on Instantiate a vnfInstance Conflict2020-11-19T13:55:17ZElian KrajaWrong SETUP on Instantiate a vnfInstance ConflictThe keyword Check resource instantiated should contain the ID of the instance to be checked.
The POST, on Instantiate a vnfInstance Conflict is done on an ID identified by the variable "instantiatedVnfInstanceId" but in Check resource i...The keyword Check resource instantiated should contain the ID of the instance to be checked.
The POST, on Instantiate a vnfInstance Conflict is done on an ID identified by the variable "instantiatedVnfInstanceId" but in Check resource instantiated keyword the check in done on the variable "vnfInstanceId"
FILE: SOL002/VNFLifecycleManagement-API/InstantiateVNFTask.robothttps://forge.etsi.org/rep/nfv/api-tests/-/issues/69Script error in VNFIndicator-API/IndividualSubscription.robot2019-06-27T07:25:14ZpasrichaScript error in VNFIndicator-API/IndividualSubscription.robotGetting script error:
failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)
on the step Check Postcondition VNF individual subscription Unmodified (Implicit)Getting script error:
failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)
on the step Check Postcondition VNF individual subscription Unmodified (Implicit)https://forge.etsi.org/rep/nfv/api-tests/-/issues/68SOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot ...2019-09-19T13:56:28ZpasrichaSOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot failing due to Discrepency in the Specifications and the schema definition for VnfIndicatorSubscription objectA few test cases in SOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot are failing due to a mismatch in the Specifications document (gs_NFV-SOL002v020401p.pdf document, page 204) and the VnfIndicatorSubscriptio...A few test cases in SOL002/VNFIndicator-API/Subscriptions.robot and IndividualSubscription.robot are failing due to a mismatch in the Specifications document (gs_NFV-SOL002v020401p.pdf document, page 204) and the VnfIndicatorSubscriptions.schema.json & VnfIndicatorSubscription.schema.json schemas given in SOL002/VNFIndicator-API/schemas directory. As per Spec, the filter property in the VnfIndicatorSubscription is of type VnfIndicatorNotificationsFilter whereas in the schema definition it is defined to be of type VnfInstanceSubscriptionFilterhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/67Schema validation failure in VNFConfiguration-API/DELETE VNF Configuration - ...2020-11-19T13:53:34ZpasrichaSchema validation failure in VNFConfiguration-API/DELETE VNF Configuration - Method not implemented Test CaseThe script “Should Be Equal ${response[0]['body']} ${input}” is trying to compare VnfConfigModification object with VnfConfiguration object which seems to have been wrongly defined in SOL002/VNFConfiguration-API/schemas/vnfConfigura...The script “Should Be Equal ${response[0]['body']} ${input}” is trying to compare VnfConfigModification object with VnfConfiguration object which seems to have been wrongly defined in SOL002/VNFConfiguration-API/schemas/vnfConfiguration.schema.json file.https://forge.etsi.org/rep/nfv/api-tests/-/issues/66Script Error in VNFConfiguration-API/Configuration.robot/Set new VNF Configur...2019-06-27T07:25:18ZpasrichaScript Error in VNFConfiguration-API/Configuration.robot/Set new VNF Configuration Test CaseGetting following error while executing Set new VNF Configuration Test Case..
Error in “Set Suite Variable {etag} ${response[0]['headers']['ETag']}
Seems due to not having $ before {etag} expressionGetting following error while executing Set new VNF Configuration Test Case..
Error in “Set Suite Variable {etag} ${response[0]['headers']['ETag']}
Seems due to not having $ before {etag} expression