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
Providing a Tractus-X Release Guideline (TRG) for code coverage by tests
Explain the topic in 2 sentences
Providing a Tractus-X Release Guideline (TRG) for static code analysis code coverage measurements and target thresholds, using Open Source methods and tools, in order to give product teams a template and best-practice example to start from or improve.
What's the benefit?
In increased quality for testing using an efficient established method, potentially avoiding issues that would then only be found in more costly tests or not discovered at all.
What are the Risks/Dependencies ?
Potentially overlaps with already existing TRG requirements? For other static code analysis measurements regarding security, dependencies, etc. TRGs are already published. See under https://eclipse-tractusx.github.io/docs/release TRG-8 Security
TRG would be defined within 25.03 release cycle, but presumably only go into effect for subsequent releases.
Code coverage thresholds as a quality gate should initially be set fairly low and then increased in subsequent releases as presumably not all product teams would immediately have e.g. a coverage of 80+%, in order to not break / prevent deployments for releases
Detailed explanation
Current implementation
A Sonarcloud solution for Tractus-X is already available https://sonarcloud.io/organizations/eclipse-tractusx/projects
But not all Tractus-X product teams have implemented or activated the code coverage functionality, and of those not all have an adequately high coverage.
Proposed improvements
Feature Team
Catena-X e.V. test management (doubleSlash, on order of the association)
Involvement of additional product teams for implementation
Contributor
ds-meberle
ds-hzimmer
ds-asmierzchalski
Additional contributors to be determined
Committer
ds-lcapellino
Additional committers to be determined
User Stories
Issue 1, linked to specific repository
Issue 2, linked to another specific repository
Acceptance Criteria
TRG for Code Coverage proposal created
TRG for Code Coverage discussed with the respective product teams, expert groups and committees
TRG for Code Coverage published
Test Cases
Test Case 1
Steps
Do something
Click something
Add something
Expected Result
Expectation
Expectation
Expectation
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
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
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)
The text was updated successfully, but these errors were encountered:
Status: Draft, not completed and refined yet
Overview
Providing a Tractus-X Release Guideline (TRG) for code coverage by tests
Explain the topic in 2 sentences
Providing a Tractus-X Release Guideline (TRG) for static code analysis code coverage measurements and target thresholds, using Open Source methods and tools, in order to give product teams a template and best-practice example to start from or improve.
What's the benefit?
In increased quality for testing using an efficient established method, potentially avoiding issues that would then only be found in more costly tests or not discovered at all.
What are the Risks/Dependencies ?
Detailed explanation
Current implementation
A Sonarcloud solution for Tractus-X is already available https://sonarcloud.io/organizations/eclipse-tractusx/projects
But not all Tractus-X product teams have implemented or activated the code coverage functionality, and of those not all have an adequately high coverage.
Proposed improvements
Feature Team
Catena-X e.V. test management (doubleSlash, on order of the association)
Involvement of additional product teams for implementation
Contributor
Additional contributors to be determined
Committer
Additional committers to be determined
User Stories
Acceptance Criteria
Test Cases
Test Case 1
Steps
Expected Result
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented:
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
The text was updated successfully, but these errors were encountered: