Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E Interoperability Tests with GEC #981

Closed
1 task
mkanal opened this issue May 15, 2024 · 6 comments
Closed
1 task

E2E Interoperability Tests with GEC #981

mkanal opened this issue May 15, 2024 · 6 comments
Assignees
Labels
spillover temporary label for spill over

Comments

@mkanal
Copy link
Contributor

mkanal commented May 15, 2024

Due Date

2024.5.24

As PO
I want conduct e2e tests with GEC interop solution
so that implementation follows agreed standards

#Links

Procedure:

  1. Check if serialpart partInstance HM001 and HM002 is present in the dDTR of GEC.
    Refer to https://confluence.catena-x.net/pages/viewpage.action?pageId=123605489
  2. Lookup corresponding C-X globalAssetId in GEC dDTR (EDC https://customer-edc.apps.dev.aws.alm.oncite.io / BPN BPNL00000007QNOK)
  3. Create SingleLevelBomAsBuilt and Serial Part
  4. Exchange notifications on these level.
  5. Provisioning of SingleLevelBomAsBuilt (Trace-X)
  6. Link C-X ID of GEC HM001 and HM002 to SerialPart Future Car X

Hints / Details

  • ...

Acceptance Criteria

  • E2E Tests conducted successfully with GEC and tests are documented in a sufficient way with evidence (screenshots or video recording)

Out of Scope

  • ...
@mkanal mkanal added this to Trace-X May 15, 2024
@mkanal mkanal moved this to next in Trace-X May 15, 2024
@ds-lcapellino ds-lcapellino moved this from next to wip in Trace-X May 24, 2024
@ds-lcapellino ds-lcapellino self-assigned this May 24, 2024
@ds-lcapellino
Copy link
Contributor

Meeting today was conducted at 11:35 to 12:30. We weren't able to successfully test the notification flow because of mismatching policies. Our DIM Wallet responded only with the Membership Credential and not in combination with the Traceability credential. Even though we configured the credential via Portal, it is not returned with the Wallet.
After GEC only used the Membership credential, IRS run into errors because of an "/$valule" at the end of the registry URL, provided by the EDC.
Jaro is currently working on a fix in IRS to address that.

@ds-lcapellino
Copy link
Contributor

The following file can be adapted and used to import a serial part, that references a GEC part:

GEC_asset_test.json

You can upload this file via the FE and only Admin role.

@RazvanZmau RazvanZmau added the spillover temporary label for spill over label May 28, 2024
@ds-mwesener ds-mwesener moved this from wip to test in Trace-X May 28, 2024
@ds-mwesener
Copy link
Contributor

We have participated on the meeting with GEC on 29.05.
We were able to successfully consume data from the registry of GEC with Trace-X.
We were unable to send notifications due to missing Traceability-Credentials within portal. We have already requested it and waiting now for the portal team to approve the requested role.

@mkanal mkanal moved this from test to review in Trace-X Jun 17, 2024
@ds-mwesener
Copy link
Contributor

Unfortunately once the portal assigned us the wallet credential. GEC did not have a running EDC anymore on the infrastructure. Therefore we did not validate that fact again. Allthough we assume that this should not be a problem regarding functionallity of trace-x and GEC.

@mkanal
Copy link
Contributor Author

mkanal commented Jun 17, 2024

PO acceptance. This procedure is now covered with various tests.

@mkanal mkanal closed this as completed Jun 17, 2024
@mkanal mkanal moved this from review to done in Trace-X Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spillover temporary label for spill over
Projects
Status: done
Development

No branches or pull requests

4 participants