01
Understanding the project
The idea in plain language.
SimTrack gives design-verification teams a purpose-built view of regression health. Instead of spreading run history across terminal logs, spreadsheets, and issue trackers, it organizes projects, named regressions, individual runs, per-test outcomes, milestones, and recurring failures in one application.
The central relationship is Project → Regression → Regression Run → Result → Failure Signature. That structure makes it possible to move from a high-level pass-rate trend down to the exact failures behind one run.
02
Core capabilities
What the project can do.
-
01
Shows project and regression dashboards with pass/fail trends over time.
-
02
Stores individual test results and groups related failures by signature.
-
03
Tracks milestones alongside regression activity.
-
04
Exposes a versioned REST API for querying records and ingesting external regression payloads.
-
05
Uses read-only access for regular users and reserves changes for staff accounts.
-
06
Includes compact and full demo-data commands for evaluation and screenshots.
03
Typical workflow
How someone uses it.
-
1
Create a project, regression definition, and any relevant milestone.
-
2
Ingest a run from CI or another tool through the API, including its test results and failure information.
-
3
Review trends on the dashboards, open an individual run, and follow repeated failure signatures across results.
04
Under the hood
Technology and design choices.
- Python 3.11+
- Django 5.2
- Django REST APIs
- SQLite
- Tailwind CSS
- Preline
05
Important considerations
What to know before using it.
- The current default database is SQLite; the roadmap includes a PostgreSQL deployment profile.
- Project-level roles and broader import formats are planned beyond the current staff-write permission model.