At a glance
| Input | Current action | Output | Boundary |
|---|---|---|---|
| Approved GitHub repository | Configure Repository, Confluence space, and Allowed paths | Report-only terminology scan scope | The connector does not create test nodes or requirement links. |
| Connector scan | Select Scan by request | Recent asynchronous jobs and Git terminology findings | Add as draft creates a glossary draft, not a trace link. |
| GitHub test file URL | Declare trace node with type test | Candidate test node with your reference | The app does not fetch the file or record a test run. |
| Test node and requirement node | Declare trace link with relation verifies and an Evidence reference | Candidate trace link | A test can also verify a document or code_reference node. |
| Candidate node or link | Another administrator selects Approve with a Review reason | Governed node or link | Four-eyes: the declarer cannot approve it. |
| Approved requirement node | Choose it in Start node, select Show trace graph, then Forward impact | Test hops under the requirement | Workspace default 5 hops and 200 links. |
| Missing endpoint or truncated graph | Review Coverage blockers | Explicit incomplete-coverage reason | Partial paths are not complete trace coverage. |
How it works
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- Use Declare trace node: type test, a title, the GitHub URL in External reference or URL, and a reason.
- Use Declare trace link: the test node as From node, the requirement as To node, relation verifies.
- Ask another administrator to approve in Trace nodes awaiting approval and Trace links awaiting approval.
- In Trace graph, choose the requirement in Start node and select Show trace graph.
- Select Forward impact and review the test hops.
- Check Coverage blockers before relying on the result.
Example
tests/payment.spec.ts covers the payment authorization requirement. An administrator declares a test node with the file permalink and a verifies link to the requirement. A second administrator approves both. Forward impact from the requirement shows the test hop.
What this does not mean
Production runs a report-only GitHub connector, with scans by request. Backend code that maps GitHub tests into trace evidence exists, but nothing in production calls it. The test node stores the URL you entered, not a hashed revision or a pass or fail result. Execution evidence needs its own record.
Related questions
Next step
Declare test nodes with exact permalinks and have a second administrator approve them before relying on test coverage traces.
View on Atlassian Marketplace