Closed kelaja closed 10 months ago
@bosserf Kannst du bitte die User Journey approven?
ich gebe in der Rolle des BO hiermit mein Approval -> selber kann ich den Haken nicht setzen: Wer macht's?
@bosserf ich übernehme 👍🏼
As discussed in yesterday's meeting and because not all test participants have Jira Access, we would document the integration and E2E tests using the following markdown table. The particpants would fill the "results" column and send their bit either as a comment to this thread or via email to @BerndRothbrust.
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Deploy Agent-Enabled Connector | Use OSS Helm-Chart. Use INT SSI/MIW Settings. Add OEM BPNL and Connector for synchronisation. | Two Pods/Services (Control Plane and Agent Data Plane) healthy. |
|
|
Perform Remote Catalogue Request | Use OEM Connector as ProviderUrl | The asset GraphAsset?oem=BehaviourTwinReliability should have at least one offer |
|
|
Check Federated Catalogue | In the agent plane log, there should be frequent synchronisation entries. | Entries associated with the OEM Connector should show "xx tuples inserted" where xx is >0 |
|
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Deploy Agent-Enabled Connector | Use Self-Compiled Images From OSS Artifacts and Own Deployment Scripts. Add SUPPLIER BPNL and Connector for synchronisation. | Two Pods/Services (Control Plane and Agent Data Plane) healthy. |
|
|
Perform Remote Catalogue Request | Use SUPPLIER Connector as ProviderUrl | The asset GraphAsset?supplier=BehaviourTwinRUL should have at least one offer |
|
|
Check Federated Catalogue | In the agent plane log, there should be frequent synchronisation entries. | Entries associated with the SUPPLIER Connector should show "xx tuples inserted" where xx is >0 |
|
|
Deploy Provisioning Agent | Use OSS Images and Own Deployment Scripts. Add a reliability binding to the existing telematics database. | One Pod/Service (Provisioning Agent) healthy. |
|
|
Access Provisioning Agent | Use SPARQL query to access reliabiility graph. | A non-emtpy result set should be returned. |
|
|
Register Graph Asset | Publish Graph Asset along KA specification with the provisioning agent service in the dataaddress. | Registration successful. |
|
|
Register Graph Policy | Publish Graph Policy along KA specification with the CONSUMER BPNL allowed. | Registration successful. |
|
|
Register Graph Contract | Publish Graph Contract along KA specification with the Graph Asset in the selector and the Graph policy for access and contract. | Registration successful. |
|
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Deploy Agent-Enabled Connector | Use OSS Helm Chart | Two Pods/Services (Control Plane and Agent Data Plane) healthy. |
|
|
Deploy Remoting Agent | Use OSS Images and Own Deployment Scripts. Add a behaviour/rul binding to the existing prognosis service with the remoting agent service as a callback. | One Pod/Service (Remoting Agent) healthy. |
|
|
Access Remoting Agent | Use SPARQL query to access behaviour/rul graph. | A non-emtpy result set should be returned. |
|
|
Register Graph Asset | Publish Graph Asset along KA specification with the remoting agent service in the dataaddress. | Registration successful. |
|
|
Register Graph Policy | Publish Graph Policy along KA specification with the OEM BPNL allowed. | Registration successful. |
|
|
Register Graph Contract | Publish Graph Contract along KA specification with the Graph Asset in the selector and the Graph policy for access and contract. | Registration successful. |
|
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Register RUL skill | Post Parameterized SPARQL to Agent/Skill Endpoint under SkillAsset?consumer=RemainingUsefulLife | Registration successful. |
|
|
Invoke RUL skill | Post VAN(s) to Agent Endpoint referring SkillAsset?consumer=RemainingUsefulLife | A non-empty result set should be returned. |
|
@drcgjung @BerndRothbrust kindly update, ThX
OK from TM @kelaja your Task now
@drcgjung
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Deploy Agent-Enabled Connector | Use OSS Helm-Chart. Use INT SSI/MIW Settings. Add OEM BPNL and Connector for synchronisation. | Two Pods/Services (Control Plane and Agent Data Plane) healthy. | control and agent plane up and running |
|
Perform Remote Catalogue Request | Use OEM Connector as ProviderUrl | The asset GraphAsset?oem=BehaviourTwinReliability should have at least one offer | offer for the GraphAsset?oem=BehaviourTwinReliability available |
|
Check Federated Catalogue | In the agent plane log, there should be frequent synchronisation entries. | Entries associated with the OEM Connector should show "xx tuples inserted" where xx is >0 | in the logs, synch job showing : Found a catalog with 1 entries for remote connector https://oem.connector. Also performed local SPARQL against catalog |
|
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Deploy Agent-Enabled Connector | Use OSS Helm Chart | Two Pods/Services (Control Plane and Agent Data Plane) healthy. | control and agent plane pods and running |
|
Deploy Remoting Agent | Use OSS Images and Own Deployment Scripts. Add a behaviour/rul binding to the existing prognosis service with the remoting agent service as a callback. | One Pod/Service (Remoting Agent) healthy. | Remoting Agent pod is running |
|
Access Remoting Agent | Use SPARQL query to access behaviour/rul graph. | A non-emtpy result set should be returned. | Non-emtpy result returned. |
|
Register Graph Asset | Publish Graph Asset along KA specification with the remoting agent service in the dataaddress. | Registration successful. | Registration done |
|
Register Graph Policy | Publish Graph Policy along KA specification with the OEM BPNL allowed. | Registration successful. | Registration done |
|
Register Graph Contract | Publish Graph Contract along KA specification with the Graph Asset in the selector and the Graph policy for access and contract. | Registration successful. | Done |
|
Step | Content | Expected | Result | Status |
---|---|---|---|---|
Register RUL skill | Post Parameterized SPARQL to Agent/Skill Endpoint under SkillAsset?consumer=RemainingUsefulLifeE2E | Registration successful. |
|
|
Invoke RUL skill | Post VAN(s) to Agent Endpoint referring SkillAsset?consumer=RemainingUsefulLifeE2E | A non-empty result set should be returned. |
|
NOTE: E2E test Executed between ADAC, Knowledge-Agent Dev Environment as OEM and ZF.
Release Test Results 23.12
Source in Catena-X Confluence and Expert Contacts here(Source only accessible for Catena-X Consortia members in current transition phase).
[x] E2E System Integrations Tests
Contact:
[x] Approval of User Journey
Artifact Repository
Best Practise
Contacts: