How-to Guide
Use Topology (System Graph)
Navigate dependency graph for impact and coverage analysis.
Objective
Navigate dependency graph for impact and coverage analysis.
Prerequisites
- Topology access
Procedure
Open Topology
Platform → Topology in Console.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Confirm organization and team context in the Console header before making changes.
Explore graph
Pan, zoom, and select nodes for dependency detail.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Note project, run, or agent IDs if you may need support escalation.
Link to coverage
Cross-reference gaps tab in Coverage area.
Navigation: Governance → Releases, Remediation, or Topology. Approver roles may be required, verify permissions first.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Team understands system dependencies and test impact.
Was this page helpful?
