SimTrack

Documentation
Source

A browser workflow for staff configuration and team analysis.

From project setup to failure triage

Typical workflow

  1. 1 Create a project and assign an optional category.
  2. 2 Create a regression definition for a stable branch, suite, or configuration workflow.
  3. 3 Add a run manually or ingest it from CI with its test results.
  4. 4 Open the regression or run page to review pass rate, counters, and failed tests.
  5. 5 Use failure-signature pages to inspect clusters of related failures.
  6. 6 Track the trend beside project milestones and delivery updates.

What the dashboard summarizes

  • Totals for projects, regressions, runs, and milestones.
  • Project-level pass rate and milestone completion progress.
  • Highest passing and highest failing regressions.
  • Upcoming milestones and top failure signatures by affected-test count.

Failure grouping is run-scoped

The current FailureSignature model belongs to one RegressionRun and groups matching failed results within that run. Global cross-run clustering is a roadmap item, so do not interpret a current signature ID as a permanent organization-wide defect identity.