Repository navigation
Verification Process Gaps #530
Description
What
Create sub-tasks for:
- Integration Testing Guideline usability (is it already good enough to create correct and complete integration tests)?
- Unit testing coverage based on specification testing (do we run all unit tests to show coverage or only the tests linked to the respective unit?)
How
No response
Estimates for realization
depends on sub-tasks
Category
- Affects Detailed Design
Requirements / Architecture
- Requirements / Architecture are not affected by this change?
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]EPIC: Verification Process Gaps[/-][+]Verification Process Gaps[/+]pahmann commentedon Jun 15, 2026
This issue was created during the audit phase, but was not resulting in an actual action/finding.
Integration testing is done already, so the guideline is deemed to be sufficient.
We are executing all unit test within one module and generate coverage on them. This answers question two.