eclipse-tractusx / sig-release

https://eclipse-tractusx.github.io/sig-release
Apache License 2.0
8 stars 10 forks source link

Knowledge Agent Release 23.12 Test Results Acceptance Criteria #92

Closed kelaja closed 10 months ago

kelaja commented 1 year ago

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).

TomBuchertTSystems commented 11 months ago

@bosserf Kannst du bitte die User Journey approven?

bosserf commented 11 months ago

ich gebe in der Rolle des BO hiermit mein Approval -> selber kann ich den Haken nicht setzen: Wer macht's?

kelaja commented 11 months ago

@bosserf ich übernehme 👍🏼

drcgjung commented 11 months ago

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.

Knowledge Agents Integration Test Suite 23.12

Knowledge Agent Integration Test Plan "Consumer" 23.12 (ADAC)

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.
  • [ ] Ok
Perform Remote Catalogue Request Use OEM Connector as ProviderUrl The asset GraphAsset?oem=BehaviourTwinReliability should have at least one offer
  • [ ] Ok
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
  • [ ] Ok

Knowledge Agent Integration Test Plan "OEM" 23.12 (BMW)

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.
  • [ ] Ok
Perform Remote Catalogue Request Use SUPPLIER Connector as ProviderUrl The asset GraphAsset?supplier=BehaviourTwinRUL should have at least one offer
  • [ ] Ok
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
  • [ ] Ok
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.
  • [ ] Ok
Access Provisioning Agent Use SPARQL query to access reliabiility graph. A non-emtpy result set should be returned.
  • [ ] Ok
Register Graph Asset Publish Graph Asset along KA specification with the provisioning agent service in the dataaddress. Registration successful.
  • [ ] Ok
Register Graph Policy Publish Graph Policy along KA specification with the CONSUMER BPNL allowed. Registration successful.
  • [ ] Ok
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.
  • [ ] Ok

Knowledge Agent Integration Test Plan "SUPPLIER" 23.12 (ZF)

Step Content Expected Result Status
Deploy Agent-Enabled Connector Use OSS Helm Chart Two Pods/Services (Control Plane and Agent Data Plane) healthy.
  • [ ] Ok
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.
  • [ ] Ok
Access Remoting Agent Use SPARQL query to access behaviour/rul graph. A non-emtpy result set should be returned.
  • [ ] Ok
Register Graph Asset Publish Graph Asset along KA specification with the remoting agent service in the dataaddress. Registration successful.
  • [ ] Ok
Register Graph Policy Publish Graph Policy along KA specification with the OEM BPNL allowed. Registration successful.
  • [ ] Ok
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.
  • [ ] Ok

Knowledge Agents E2E Test Suite 23.12

Knowledge Agents E2E Test Plan "CONSUMER" 23.12 (ADAC)

Step Content Expected Result Status
Register RUL skill Post Parameterized SPARQL to Agent/Skill Endpoint under SkillAsset?consumer=RemainingUsefulLife Registration successful.
  • [ ] Ok
Invoke RUL skill Post VAN(s) to Agent Endpoint referring SkillAsset?consumer=RemainingUsefulLife A non-empty result set should be returned.
  • [ ] Ok
kelaja commented 11 months ago

@drcgjung @BerndRothbrust kindly update, ThX

BerndRothbrust commented 11 months ago

OK from TM @kelaja your Task now

dreni commented 11 months ago

@drcgjung

Knowledge Agent Integration Test Plan "Consumer" 23.12 (ADAC)

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
  • [x] Ok
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
  • [x] Ok
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
  • [x] Ok
RohitKumar-ZF commented 11 months ago
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
  • [x] Ok
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
  • [x] Ok
Access Remoting Agent Use SPARQL query to access behaviour/rul graph. A non-emtpy result set should be returned. Non-emtpy result returned.
  • [x] Ok
Register Graph Asset Publish Graph Asset along KA specification with the remoting agent service in the dataaddress. Registration successful. Registration done
  • [x] Ok
Register Graph Policy Publish Graph Policy along KA specification with the OEM BPNL allowed. Registration successful. Registration done
  • [x] Ok
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
  • [x] Ok
dreni commented 10 months ago

Knowledge Agents E2E Test Plan "CONSUMER" 23.12 (ADAC)

Step Content Expected Result Status
Register RUL skill Post Parameterized SPARQL to Agent/Skill Endpoint under SkillAsset?consumer=RemainingUsefulLifeE2E Registration successful.
  • [x] Ok
Invoke RUL skill Post VAN(s) to Agent Endpoint referring SkillAsset?consumer=RemainingUsefulLifeE2E A non-empty result set should be returned.
  • [x] Ok

NOTE: E2E test Executed between ADAC, Knowledge-Agent Dev Environment as OEM and ZF.