[Tractus-X EDC] Improve Compatibility Tests

[lgblaumeiser]

Overview

Explain the topic in 2 sentences

Compatibility Tests between a current connector development and former versions are established with the last connector release. The established infrastructure is only rudimentary available and needs to be brought to a level, that provides a qualitative result concerning the compatibility.

What's the benefit?

Significant reduction of incompatibility risk between different version of the connector.

What are the Risks/Dependencies ?

none

Detailed explanation

• Evaluate synergies between existing e2e tests and compatibility tests to prevent double maintenance of test cases
• Improve existing coverage of use cases in additional test cases
• Invent mechanisms to ensure outside compatibility of visible data structures defined by the DSP (e.g. the Catalog)

Feature Team

Contributor

• BMW
• Cofinity-X

Committer

• @lgblaumeiser
• @rafaelmag110
• @ndr-brt

User Stories

• Issue 1, linked to specific repository
• Issue 2, linked to another specific repository

Acceptance Criteria

• A documented test concept for e2e and compatibility tests
• Test cases for known inconsistencies are implemented
• Risk assessment of the remaining risks do not show remaining known major risks

Test Cases

n/a

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
    • CX-0010 Business Partner Number
    • CX-0013 Identity of Member Companies
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0049 DID Document Schema
    • CX-0050 Framework Agreement Credential
    • CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
    • CX-0001 EDC Discovery API
    • CX-0002 Digital Twins in Catena-X
    • CX-0018 Data Space Connectivity (EDC)
    • CX-0126 Industry Core: Part Type 2.0.0
    • CX-0127 Industry Core: Part Instance 2.0.0
  • Data Format:
    • The data model is based on a published Semantic Model
• The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)