[R25.03] DCM: Additional Content E2E Test

[LukasSchmetz]

Description

Add further E2E Test Journeys beyond the Base Journey to the Development View in the DCM KIT.

Feature Team

Contributor

• Philipp Mai
• Markus Wagner
• Lukas Schmetz
• Katharina Zipse

Committer

• @stephanbcbauer
• Committer group in PR as assignee

Explain the topic in 2 sentences

Add further E2E Test Journeys beyond the Base Journey to the Development View in the DCM KIT. This includes test cases and data.

What's the benefit?

Availability to execute additional testing of DCM functionalities.

What are the Risks/Dependencies ?

Low Risks / No Dependencies to other teams

Detailed explanation

Additional content for testing purposes will be added to the Development View of the DCM KIT.

Current implementation

N/A

Proposed improvements

Additional test journeys including test data available.

User Stories

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

Acceptance Criteria

• [ ] New advanced test journeys developed
• [ ] New advanced test journeys written
• [ ] New advanced test journeys added to Development View in DCM KIT

Architectural Relevance

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

• [ ] 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)
  • 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)

[stephanbcbauer]

@LukasSchmetz , @ClosedSourcerer I just replaced the additional information section ;)

[ClosedSourcerer]

Finalize the following three testing journeys:

• Demand volatility metrics journey
• Simulated delta production journey
• Load factors journey

Decide if additional journey are to be included

This required modifying the following files:

• ..\docs-kits\kits\Demand and Capacity Management Kit\development-view\test-customer.md
• ..\docs-kits\kits\Demand and Capacity Management Kit\development-view\test-supplier.md

Adhere to the existing KIT E2E-Tests:

• Naming conventions
• Cucumber
• Gherkin
• Structure
• CodeBlocks

Technical tests do not need to be written for those journeys Business tests are what is in demand --> @LukasSchmetz I need support from a subject matter experts, that defines business scenarios/tests in such a way, that the amounts etc. make sense in a business context.

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Inbox. ⇾ Only features with status backlog are considered in open planning
• Please add missing sections from the feature template, or fill them out