You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the EDC has well established quality assurance mechanisms which lack transparency. It is not possible to get an overview of what has been tested without a detailed code view.
What's the benefit?
Quality of the EDC can be shown on a more abstract level than code.
What are the Risks/Dependencies ?
No breaking changes, no risks
Detailed explanation
Introduction of code coverage measurement
Introduction of a test report
Better documentation of e2e tests
Improvements concerning e2e and compatibility tests
A release of the EDC comes with a test report that describes the state of the different testing levels, on lower levels information like coverage whereas on higher levels a high-level description of single test cases executed
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
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
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)
The text was updated successfully, but these errors were encountered:
lgblaumeiser
changed the title
Improve transparency of Tractus-X EDC quality assurance mechanisms
[Tractus-X EDC] Improve transparency of quality assurance mechanisms
Jan 31, 2025
Overview
Explain the topic in 2 sentences
Currently, the EDC has well established quality assurance mechanisms which lack transparency. It is not possible to get an overview of what has been tested without a detailed code view.
What's the benefit?
Quality of the EDC can be shown on a more abstract level than code.
What are the Risks/Dependencies ?
No breaking changes, no risks
Detailed explanation
Feature Team
Contributor
Committer
User Stories
Acceptance Criteria
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.
Additional information
The text was updated successfully, but these errors were encountered: