Closed jzbmw closed 9 months ago
FYI I corrected the ESS testdatafile ESS_Testdata_v2.0.0-AsPlanned.json since the "Vehicle D" ids were not completely correct. Changes pushed to Pawels branch feature/TRI-1658-infected-supply-chain-on-first-tier-level. Please note the changes are not uploaded yet.
Hi @ds-psosnowski!
I was able to detect an issue for requests on first incident level. See e.g. request
{ "key": { "globalAssetId": "urn:uuid:3a2a1ca9-c6c1-49c7-a7ae-1dfc5fb9881f", "bpn": "BPNL00ARBITRARY8" }, "incidentBPNSs": ["BPNS0ARBITRARY10"], "bomLifecycle": "asPlanned" }
which is expected to have the "bpnl" result "BPNS0ARBITRARY10" but is "BPNL00000004FAIL" instead:
Could you have a look please?
Please also have a look on scenario with more then one node with affected BPN. E. for this request:
{ "key": { "globalAssetId": "urn:uuid:aad27ddb-43aa-4e42-98c2-01e529ef127c", "bpn": "BPNL00ARBITRARY1" }, "incidentBPNSs": ["BPNS00000003B6LU"], "bomLifecycle": "asPlanned" }
we are expecting two entries in the impactedSuppliersOnFirstTier array. Currently there is only one.
No more issues could be found during testing on ESS-INT with branch feature/TRI-1658-infected-supply-chain-on-first-tier-level. The first tier level with infection is detected correctly, see e.g. request:
{ "key": { "globalAssetId": "urn:uuid:3a2a1ca9-c6c1-49c7-a7ae-1dfc5fb9881f", "bpn": "BPNL00ARBITRARY8" }, "incidentBPNSs": ["BPNS0ARBITRARY11"], "bomLifecycle": "asPlanned" }
and impactedSupplierOnFirstTier result:
"submodels": [ { "identification": null, "aspectType": "supply_chain_impacted", "payload": { "supplyChainImpacted": "Yes", "impactedSuppliersOnFirstTier": { "bpnl": "BPNL00ARBITRARY10", "hops": 2 }...
Tavern tests have been added to same branch. This is the outcome:
Ticket is ready for PO-review. FYI @jzbmw
As user I want that the sub-tree where infection was found is known so that I am able to address the correct supplier for more investigation
Hints / Details
Outcome / Acceptance Criteria
Outcome
Acceptance Criteria
Out of Scope