documentation
Coverage
How Bloom finds requirements with no test cases or only draft coverage, and where to read the result.
Coverage analysis flags requirements with no test cases or only draft coverage.
How coverage is counted
Section titled “How coverage is counted”- A requirement is covered by the test cases that
verifyit. See Typed links. - A draft test case verifies nothing. A requirement whose only test cases are drafts has only draft coverage.
- Coverage is counted the same way everywhere in Bloom.
- Inline
#tags arereferenceslinks. They are excluded from coverage and traceability.
Where to read it
Section titled “Where to read it”- Traceability matrix. The matrix is paginated. Every project export and report is offered from one Export menu on the traceability page.
- Verification dossier. A PDF report that lists each requirement with the test cases that verify it and their last results.
- Other PDF reports. The traceability matrix and the test cases are also available as PDF reports on the report letterhead. An administrator can upload a company logo in Settings. It renders at the top left of the letterhead, alongside the EmbedLabs tamper-evidence footer, which is always present.
- Test case exports. Export test cases as Markdown, CSV, XML and PDF, with every step row.
An export holds only what the user may see. Artefacts hidden from external users and document types outside their allowlist are left out. See Roles and access.
Execution results from Bud
Section titled “Execution results from Bud”When Bloom is connected to Bud, Bud posts one aggregated execution outcome per tc_id to Bloom, which updates the matching test case and its campaign line items.



