NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2019-06-26T12:48:38Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/56Invalid log level 'Postcondition indicators exist'.2019-06-26T12:48:38ZjonnadaInvalid log level 'Postcondition indicators exist'.Interface: VNF/VNFIndicators
Test Case: DELETE all VNF Indicators - Method not implementedInterface: VNF/VNFIndicators
Test Case: DELETE all VNF Indicators - Method not implementedhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/55TypeError: argument of type 'int' is not iterable2019-06-26T12:49:09ZjonnadaTypeError: argument of type 'int' is not iterableInterface: VNF/VNFIndicators
Test Case: (1)Get all VNF Indicators with invalid authorization token
(2) Get all VNF Indicators without authorization token
Issue at:
Check HTTP Response Status Code Is 40x
Should Contain ...Interface: VNF/VNFIndicators
Test Case: (1)Get all VNF Indicators with invalid authorization token
(2) Get all VNF Indicators without authorization token
Issue at:
Check HTTP Response Status Code Is 40x
Should Contain Any ${response[0]['status']} 401 403
Log Status code validatedElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/54Resolving variable '${response.body}' failed: AttributeError: 'list' object h...2019-06-26T12:49:51ZjonnadaResolving variable '${response.body}' failed: AttributeError: 'list' object has no attribute 'body'Should this be ${response[0]['body']} ?
Interface: VNF/VNFIndicators
Test Case: Get all VNF IndicatorsShould this be ${response[0]['body']} ?
Interface: VNF/VNFIndicators
Test Case: Get all VNF IndicatorsElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/53File not found error *.schema.json2019-06-27T07:29:12ZjonnadaFile not found error *.schema.jsonFile not found issue at "Check HTTP Response Body Json Schema Is *". This has been the same for all test cases with check HTTP response body.
Interface: VNF/IndividualSubscription (applies to other interfaces and test cases as well)File not found issue at "Check HTTP Response Body Json Schema Is *". This has been the same for all test cases with check HTTP response body.
Interface: VNF/IndividualSubscription (applies to other interfaces and test cases as well)https://forge.etsi.org/rep/nfv/api-tests/-/issues/52Dependency not met: test case 'Send VNF configuration' not found, wanted 'PASS'2020-11-19T13:48:00ZjonnadaDependency not met: test case 'Send VNF configuration' not found, wanted 'PASS'Interface: VNF/configuration
Test Case: Set new VNF Configuration - HTTP Etag precondition unsuccessfulInterface: VNF/configuration
Test Case: Set new VNF Configuration - HTTP Etag precondition unsuccessfulAHMADABBAHMADABBhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/51Wrong variable is used in the URI in SOL003/VNFPackageManagement-API/VNFPacka...2019-06-26T12:54:38ZElian KrajaWrong variable is used in the URI in SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robotIn Line 62 the variable related to the vnfPackage id should be ${onboardingStateVnfPkgId} not ${erroneousVnfPkgId}In Line 62 the variable related to the vnfPackage id should be ${onboardingStateVnfPkgId} not ${erroneousVnfPkgId}Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/50Content-Type check on octet-stream should be removed in SOL003/VNFPackageMana...2019-09-19T13:54:54ZElian KrajaContent-Type check on octet-stream should be removed in SOL003/VNFPackageManagement-API/VNFPackageArtifacts.robotLines 15/16 should be removed
`
${contentType}= Output response headers Content-Type
Should Contain ${contentType} ${CONTENT_TYPE_OCTET}
`Lines 15/16 should be removed
`
${contentType}= Output response headers Content-Type
Should Contain ${contentType} ${CONTENT_TYPE_OCTET}
`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/49Handling text or ZIP vnfds2021-09-22T08:35:46ZElian KrajaHandling text or ZIP vnfds* [ ] NFVO_VNFD_PLAIN not used. Remove from variables file
* [ ] VNFD_PLAIN in variables.txt is not used properly. Should be created VNFD_ZIP and the two variables should be indipendent
* [ ] Review logic of the test cases* [ ] NFVO_VNFD_PLAIN not used. Remove from variables file
* [ ] VNFD_PLAIN in variables.txt is not used properly. Should be created VNFD_ZIP and the two variables should be indipendent
* [ ] Review logic of the test casesElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/48[GENERIC] Asynchronous vs Synchronous should be alternately executed based on...2020-11-18T18:56:34ZElian Kraja[GENERIC] Asynchronous vs Synchronous should be alternately executed based on availabilityhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/47[GENERIC] Mismatching between Accept header and returned object2021-02-09T08:13:22ZElian Kraja[GENERIC] Mismatching between Accept header and returned objectIn all test cases, should be coherence between the Accept header and the expectation of the test
If excepted type is different from json (zip or plain text), avoid check on Content-Type application/jsonIn all test cases, should be coherence between the Accept header and the expectation of the test
If excepted type is different from json (zip or plain text), avoid check on Content-Type application/jsonhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/46Wrong URI at SOL005/NSDManagement-API/NSDescriptors.robot2019-06-26T12:59:26ZElian KrajaWrong URI at SOL005/NSDManagement-API/NSDescriptors.robotOn test case GET all Network Service Descriptors (Negative: Not found)
`Line 92: GET ${apiRoot}/${apiName}/${apiVersion}/ns_descriptors`
Should be
`GET ${apiRoot}/${apiName}/${apiVersion}/ns_descriptor`
in order to generate a...On test case GET all Network Service Descriptors (Negative: Not found)
`Line 92: GET ${apiRoot}/${apiName}/${apiVersion}/ns_descriptors`
Should be
`GET ${apiRoot}/${apiName}/${apiVersion}/ns_descriptor`
in order to generate a not foundElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/45SSL Verification need to be disabled on all test suites2020-11-18T18:44:35ZElian KrajaSSL Verification need to be disabled on all test suitesIn order to avoid failures on HTTPS requests, all test suites should disable ssl verification with:
`REST https://${IP}:${PORT} ssl_verify=false`In order to avoid failures on HTTPS requests, all test suites should disable ssl verification with:
`REST https://${IP}:${PORT} ssl_verify=false`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/44SOL003-VNFLifeCycleManagement-API - subscriptions.schema.json: error on Permi...2021-06-03T08:49:18ZOliviaSOL003-VNFLifeCycleManagement-API - subscriptions.schema.json: error on Permitted values of notificationTypesIt's now ["ThresholdCrossedNotification", "PerformanceInformationAvailableNotification"]
should be ["VnfLcmOperationOccurrenceNotification", "VnfIdentifierCreationNotification", "VnfIdentifierDeletionNotification"]It's now ["ThresholdCrossedNotification", "PerformanceInformationAvailableNotification"]
should be ["VnfLcmOperationOccurrenceNotification", "VnfIdentifierCreationNotification", "VnfIdentifierDeletionNotification"]AHMADABBAHMADABBhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/43Synchronous Grant: Response is not treated as a valid json. Elements have sin...2020-11-18T18:37:05ZElian KrajaSynchronous Grant: Response is not treated as a valid json. Elements have single quote instead of double quotes.AHMADABBAHMADABBhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/42All NO RANGE TD should be removed since are the same with the "classic" GET a...2019-03-19T13:40:49ZElian KrajaAll NO RANGE TD should be removed since are the same with the "classic" GET already provided in the test suitesThe TD "NO RANGE" has the same behaviour as the classic GET. All related TDs should be removed from the test suites.The TD "NO RANGE" has the same behaviour as the classic GET. All related TDs should be removed from the test suites.Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/41Schema issue in subscriptions.schema.json. It is not an array as expected2019-03-19T13:40:04ZElian KrajaSchema issue in subscriptions.schema.json. It is not an array as expectedsubscriptions.schema.json is not an array as should besubscriptions.schema.json is not an array as should beElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/40Typo on SOL003/VNFLifecycleManagement-API/Subscriptions.robot2019-03-19T13:40:59ZElian KrajaTypo on SOL003/VNFLifecycleManagement-API/Subscriptions.robotIOError: [Errno 2] No such file or directory: 'schemas//Subscriptions.schema.json'.
File is named subscriptions.schema.jsonIOError: [Errno 2] No such file or directory: 'schemas//Subscriptions.schema.json'.
File is named subscriptions.schema.jsonElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/39Schema issue on VnfLcmOpOccs.schema.json. It is not an array as expected2019-03-19T13:41:10ZElian KrajaSchema issue on VnfLcmOpOccs.schema.json. It is not an array as expectedVnfLcmOpOccs.schema.json is not an arrayVnfLcmOpOccs.schema.json is not an arrayElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/38Typo on VNFLifecycleManagement-API/TerminateVNFTask.robot2019-03-19T13:41:25ZElian KrajaTypo on VNFLifecycleManagement-API/TerminateVNFTask.robotIOError: [Errno 2] No such file or directory: '.../VNFLifecycleManagement-API/jsons/terminateVnFRequest.json'.
File name is terminateVnfRequest.jsonIOError: [Errno 2] No such file or directory: '.../VNFLifecycleManagement-API/jsons/terminateVnFRequest.json'.
File name is terminateVnfRequest.jsonElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/37Keyword: "Parametrize Check resource not instantiated" should be parametrized2019-03-19T13:41:33ZElian KrajaKeyword: "Parametrize Check resource not instantiated" should be parametrizedIn SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot and other operations on vnfInstances the keyword must be parametrized to avoid failure where test cases uses different vnfInstanceIdsIn SOL003/VNFLifecycleManagement-API/ScaleVNFTask.robot and other operations on vnfInstances the keyword must be parametrized to avoid failure where test cases uses different vnfInstanceIdsElian KrajaElian Kraja