api-tests issueshttps://forge.etsi.org/rep/nfv/api-tests/-/issues2021-05-28T07:10:56Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/183SOL002/vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} API V2.4.1 ...2021-05-28T07:10:56ZguptanavSOL002/vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId}} API V2.4.1 GET methodWhen testing case '**GET Individual Subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f97f...When testing case '**GET Individual Subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/0f3e6f190ee24cf912e1830c827d6ef5/f97f0fb8-e205-4809-b9d5-1d63397702c4.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/182SOL003/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 GET method2021-05-28T07:12:07ZguptanavSOL003/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 GET methodWhen testing case '**GET Subscriptions**' it got failed with
ValidationError: Validation error for schema Subscriptions.schema.json: ['VnfLcmOperationOccurrenceNotification', 'VnfIdentifierCreationNotification', 'VnfIdentifierDeletionN...When testing case '**GET Subscriptions**' it got failed with
ValidationError: Validation error for schema Subscriptions.schema.json: ['VnfLcmOperationOccurrenceNotification', 'VnfIdentifierCreationNotification', 'VnfIdentifierDeletionNotification'] is not of type 'string'
*Attached are complete logs of the same* :
[eef8526a-2352-4e1a-92bc-b2d5b0ef6d0a.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/23aba39ffede1974c3ea60b0e6897311/eef8526a-2352-4e1a-92bc-b2d5b0ef6d0a.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/181SOL002/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 POST and GET method2021-05-28T07:12:01ZguptanavSOL002/vnflcm/{apiMajorVersion}/subscriptions API V2.4.1 POST and GET methodWhen testing case
* '**POST Create a new subscription**' it got failed with error message KeyError: '\n "filter"'
* '**GET Subscription**s' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: ...When testing case
* '**POST Create a new subscription**' it got failed with error message KeyError: '\n "filter"'
* '**GET Subscription**s' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[c2d987d0-fa4e-4736-8a54-39da4b21ae11.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/e9da042e5797c9be8c6eb6b169eac337/c2d987d0-fa4e-4736-8a54-39da4b21ae11.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/180SOL003 and SOL002 /vnf_lcm_op_occs/${vnfLcmOpOccId}/failAPI V2.4.1 POST method2021-05-28T07:12:17ZguptanavSOL003 and SOL002 /vnf_lcm_op_occs/${vnfLcmOpOccId}/failAPI V2.4.1 POST methodWhen testing case '**POST Fail operation task**' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperati...When testing case '**POST Fail operation task**' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/cad498e8efb7d12e3fe26bd938e9a292/83880b26-4b18-4afd-ac97-f42efc8664d8.VNFLifecycleManagement-API.FailOperationTask.log.html)
[733392c2-93bb-45ca-83ab-e7741c62022c.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/e8dd8fd9cb1e39443bb3a0122aef4304/733392c2-93bb-45ca-83ab-e7741c62022c.VNFLifecycleManagement-API.FailOperationTask.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/179SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 ...2021-05-28T07:11:55ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 GET methodWhen testing case '**Get information about multiple VNF instances**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of ...When testing case '**Get information about multiple VNF instances**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[f67f0af5-65d2-4106-8fa8-8098ce53ef4c.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/41a8c1b4725743830389cc3852d5c57e/f67f0af5-65d2-4106-8fa8-8098ce53ef4c.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/177SOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 ...2021-05-28T07:11:49ZguptanavSOL003/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId} API V2.4.1 GET methodWhen testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9-...When testing case '**Get information about multiple VNF instances**' it got failed with error message 'resourse was not found.' comes. API path is wrong.${vnfLcmOpOccId} is missing.
*Attached are complete logs of the same* :
[b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/c9f63183b407c8dbcc692f1f007f943d/b5d0cdb9-28bc-4dec-bf46-f27351c7c776.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/176SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs V2.4.1 GET method2021-05-28T07:11:24ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs V2.4.1 GET methodWhen testing case '**GET status information about multiple VNF LCM operation occurrences**' HTTP return status is 200 but expected is 202
*Attached are complete logs of the same* :
[8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleMan...When testing case '**GET status information about multiple VNF LCM operation occurrences**' HTTP return status is 200 but expected is 202
*Attached are complete logs of the same* :
[8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html](/uploads/aae5da20875d22faac95ceeeb09095ee/8c9344dd-510f-4985-89fc-f3cbcbf89bf5.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/175SOL003 and SOL002 /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GE...2021-05-28T07:11:41ZguptanavSOL003 and SOL002 /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GET V2.4.1When testing case '**Get Information about an individual VNF Instance**' some 'Expected property 'response headers ETag' was not found.' comes but HTTP return status is 200
*Attached are complete logs of the same* :
[e07f6a91-4872-459c...When testing case '**Get Information about an individual VNF Instance**' some 'Expected property 'response headers ETag' was not found.' comes but HTTP return status is 200
*Attached are complete logs of the same* :
[e07f6a91-4872-459c-b148-824e5dae8802.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/c9b6f7e4d29402f814241dc7ff88e32a/e07f6a91-4872-459c-b148-824e5dae8802.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)
[1b94e0bb-0d8e-459d-b585-27c0d759e7a9.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/fcc88ad00ae8a612c184c2aba209ae5d/1b94e0bb-0d8e-459d-b585-27c0d759e7a9.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/174SOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}/fail API POS...2021-06-03T08:49:17ZguptanavSOL002/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}/fail API POST V2.6.1When testing case 'POST Fail operation task' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationT...When testing case 'POST Fail operation task' some Internal Server Error and Can not find requested vnf instance
*Attached are complete logs of the same* :
[a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationTask.log.html](/uploads/85820332f35826f2c631de05e92cff32/a05010be-3af1-4aa1-b331-03d6659b9b1d.VNFLifecycleManagement-API.FailOperationTask.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/173SOL002 and SOL003 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} D...2021-05-28T07:11:32ZguptanavSOL002 and SOL003 /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} DELETE V2.6.1When testing cases' '**DELETE an individual subscription**' HIVE TAP return 204 but expected is 405
*Attached are complete logs of the same* :
[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log...When testing cases' '**DELETE an individual subscription**' HIVE TAP return 204 but expected is 405
*Attached are complete logs of the same* :
[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/8bc7401b73e41327fb16f4f1bbe40ba7/8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html)
[fd116d50-052f-475c-9fb0-5fc382afdd73.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/275995211db731eeaf15f81f8536e16d/fd116d50-052f-475c-9fb0-5fc382afdd73.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/172SOL002 /vnflcm/{apiMajorVersion}/subscriptions POST V2.6.12021-03-18T06:28:46ZguptanavSOL002 /vnflcm/{apiMajorVersion}/subscriptions POST V2.6.1When testing cases' **POST Create a new subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[...When testing cases' **POST Create a new subscription**' it got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/2ac94ad8afddc6eb3f47fb87a88c9567/a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/171SOL002 /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs, /vnflcm/{apiMajorVersion}/v...2021-05-28T07:11:07ZguptanavSOL002 /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs, /vnflcm/{apiMajorVersion}/vnf_lcm_op_occs/${vnfLcmOpOccId}, /vnflcm/{apiMajorVersion}/subscriptions and /vnflcm/{apiMajorVersion}/subscriptions/${subscriptionId} GET V2.6.1When testing cases
* '**GET status information about multiple VNF LCM operation occurrences**'
* '**Get information about multiple VNF instances**
* '**GET Subscriptions**'
* '**GET Individual Subscription**'
they all got fai...When testing cases
* '**GET status information about multiple VNF LCM operation occurrences**'
* '**Get information about multiple VNF instances**
* '**GET Subscriptions**'
* '**GET Individual Subscription**'
they all got failed with error message 'FileNotFoundError: [Errno 2] No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'.' comes.
*Attached are complete logs of the same* :
[1011cde5-cbc8-4e78-abae-7f1e04825cde.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html](/uploads/2ca2ec54d04c7e8bd9ad493b66a4a1a2/1011cde5-cbc8-4e78-abae-7f1e04825cde.VNFLifecycleManagement-API.VnfLcmOperationOccurences.log.html)[e040fbc1-df19-4e79-a62a-1920dc7d9649.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html](/uploads/ac24de9919bac234e6149aa8ad3294c6/e040fbc1-df19-4e79-a62a-1920dc7d9649.VNFLifecycleManagement-API.IndividualVnfLcmOperationOccurence.log.html)[a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html](/uploads/59eb245f335e2fa95b7c48e37c9c0b83/a1d86506-aee1-4893-ba5b-368a4e0a2f8c.VNFLifecycleManagement-API.Subscriptions.log.html)[8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html](/uploads/708c1228e41dbbcf897ede19b5953c51/8fd09181-deab-44dd-84f4-b5d96f391396.VNFLifecycleManagement-API.IndividualSubscription.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/170SOL002 /vnflcm/{apiMajorVersion}/vnf_instances POST, /vnflcm/{apiMajorVersion...2021-05-28T07:11:16ZguptanavSOL002 /vnflcm/{apiMajorVersion}/vnf_instances POST, /vnflcm/{apiMajorVersion}/vnf_instances GET and /vnflcm/{apiMajorVersion}/vnf_instances/${vnfInstanceId} GET V2.6.1When testing cases
* '**Create a new vnfInstance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**GET information about multiple VNF insta...When testing cases
* '**Create a new vnfInstance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**GET information about multiple VNF instances**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 201
* '**Get Information about an individual VNF Instance**' some validation error for schema vnfInstance.schema.json: '*vnfPkgInfoId*' is a required property comes but HTTP return status is 200
*Attached are complete logs of the same* :
[82461eeb-3b91-49b0-b713-9f177d06e830.VNFLifecycleManagement-API.VNFInstances.log.html](/uploads/fe2c3cf96711fd950ab429de66f8d8e4/82461eeb-3b91-49b0-b713-9f177d06e830.VNFLifecycleManagement-API.VNFInstances.log.html)[d7ccf875-e3c1-4823-a5fa-6f6e21790574.VNFLifecycleManagement-API.IndividualVNFInstance.log.html](/uploads/bdde85d95aa68e13898197f9a2b25354/d7ccf875-e3c1-4823-a5fa-6f6e21790574.VNFLifecycleManagement-API.IndividualVNFInstance.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/169SOL005 NS LCM Individual NSInstance v2.7.1 - delete with conflict cannot be r...2021-03-03T17:59:25ZGiacomo BerniniSOL005 NS LCM Individual NSInstance v2.7.1 - delete with conflict cannot be run due to previous test executionThis test uses a single nsInstanceId variable, however, when it gets deleted at the “delete” test, then it can’t be found at the “delete conflict” testThis test uses a single nsInstanceId variable, however, when it gets deleted at the “delete” test, then it can’t be found at the “delete conflict” testhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/168TST issue in '/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003 v2.6.1 api2021-03-09T14:17:25ZguptanavTST issue in '/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003 v2.6.1 apiwhen testing **/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003** api
HTTP return code is 200 but test suite is fail as it is expecting 202 return code
[ocss_TST_ISSUE.txt](/uploads/e8d79d9fe5cd48e124226acae9be210b/ocss_TST_ISSUE.txt)when testing **/vnflcm/{apiMajorVersion}/vnf_lcm_op_occs SOL003** api
HTTP return code is 200 but test suite is fail as it is expecting 202 return code
[ocss_TST_ISSUE.txt](/uploads/e8d79d9fe5cd48e124226acae9be210b/ocss_TST_ISSUE.txt)https://forge.etsi.org/rep/nfv/api-tests/-/issues/167POST Terminate a vnfInstance Conflict returned http code 202 SOL003 VNFLifecy...2021-06-03T08:49:17ZyaoyuyPOST Terminate a vnfInstance Conflict returned http code 202 SOL003 VNFLifecycleManagementAPI v2.6.1According to the specifitiaction, when termanting a not-instantiate state vnf instance, it should return http code 409, while the code check if it is 202.
specificaition SOL003 V2.6.1 Chapter 5.4.8.3.1
Typically, this is due to the fact...According to the specifitiaction, when termanting a not-instantiate state vnf instance, it should return http code 409, while the code check if it is 202.
specificaition SOL003 V2.6.1 Chapter 5.4.8.3.1
Typically, this is due to the fact that the "Individual VNF
instance" resource is in NOT_INSTANTIATED state,
that another lifecycle management operation is
ongoing, or that a required (see note) child attribute of
the "extensions" attribute has not been set.https://forge.etsi.org/rep/nfv/api-tests/-/issues/166Wrong data type for links SOL005 VNFPackageManagementAPI v2.6.12021-06-03T08:49:17ZyaoyuyWrong data type for links SOL005 VNFPackageManagementAPI v2.6.1Test failed beacause meeting the error as followed:
ValidationError: Validation error for schema links.schema.json: {'self': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5'}, 'packageContent': {'href': '/vnfpkgm/...Test failed beacause meeting the error as followed:
ValidationError: Validation error for schema links.schema.json: {'self': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5'}, 'packageContent': {'href': '/vnfpkgm/v1/vnf_packages/04d7a289-50d7-42c6-bcab-795712f0c3a5/package_content'}} is not of type 'array'
refered to the links.schema.json file, the code is
`"type": "array",`
but according to the sol specification (SOL005 v2.6.1 9.5.2.5 Type: VnfPkgInfo), the links's data type should be Structure (inlined)
[249cd2b9-168c-4272-80ff-0d348154432c.VNFPackageManagement-API.VNFPackages.log.html](/uploads/0e4260747fe1eabc4af0a4475b20f9de/249cd2b9-168c-4272-80ff-0d348154432c.VNFPackageManagement-API.VNFPackages.log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/165Using the same parameter when checking full size and Content-length SOL003 v2...2021-06-03T08:49:17ZyaoyuyUsing the same parameter when checking full size and Content-length SOL003 v2.6.1 VNFPackageManagementAPISame parameter is used to check for the file size and range size.and they can only be eqaul if the range size is same with the file size.
eg. the file size is 51 and the request range is range :bytes=0-50
so the response in Content-R...Same parameter is used to check for the file size and range size.and they can only be eqaul if the range size is same with the file size.
eg. the file size is 51 and the request range is range :bytes=0-50
so the response in Content-Range will be bytes 0-50/51
and the Content-Length will be 51 too
Another situation is the file size is 1000 and the request range is range :bytes=0-50
so the response in Content-Range will be bytes 0-50/1000
and the Content-Length will be 51
The parameter used to be ${full_size} and ${length} but it is changed now.
```
Check HTTP Response Header Content-Range Is Present and Matches the requested range
Log Check Content-Range HTTP Header
Should Contain ${response['headers']} Content-Range
Should Be Equal As Strings ${response['headers']['Content-Range']} bytes ${range}/${full_length}
Log Header Content-Range is present
Check HTTP Response Header Content-Length Is Present and Matches the requested range length
Log Check Content-Length HTTP Header
Should Contain ${response['headers']} Content-Length
Should Be Equal As Integers ${response['headers']['Content-Length']} ${full_length}
Log Header Content-Length is present
```https://forge.etsi.org/rep/nfv/api-tests/-/issues/163SOL005 NSDManagement IndividualSubscription PUT & PATCH methods fail to evalu...2021-03-04T08:26:19ZvignaudSOL005 NSDManagement IndividualSubscription PUT & PATCH methods fail to evaluate JsonThose methods fail with error message :
`Evaluating expression 'json.loads('''{'id': '527bb09d-29e2-4025-962e-1e21134a6836', <...SNIP...>''')' failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 ...Those methods fail with error message :
`Evaluating expression 'json.loads('''{'id': '527bb09d-29e2-4025-962e-1e21134a6836', <...SNIP...>''')' failed: JSONDecodeError: Expecting property name enclosed in double quotes: line 1 column 2 (char 1)`
[log.html](/uploads/38b97df5a0ca96e185e8c0d123fc86bf/log.html)https://forge.etsi.org/rep/nfv/api-tests/-/issues/162SOL005 IndividualNSDescriptor nsdUsageState is retreived on a 4042021-06-03T08:49:17ZvignaudSOL005 IndividualNSDescriptor nsdUsageState is retreived on a 404In `GET Individual Network Service Descriptor Information with invalid resource identifier` test case fail because
`Resolving variable '${response['body']['nsdUsageState']}' failed: KeyError: 'nsdUsageState'`
Of course it does not exi...In `GET Individual Network Service Descriptor Information with invalid resource identifier` test case fail because
`Resolving variable '${response['body']['nsdUsageState']}' failed: KeyError: 'nsdUsageState'`
Of course it does not exist on a ProblemDetails response.
[log.html](/uploads/4085f817643c1c793a5cc186e5a6389f/log.html)