Solution · Test Management
Structure, history and bugs — in one place
Progon is not just a recording tool. It is a complete workspace for QA: project and scenario hierarchy, test runs with history, bug tracking, checklists and custom fields with a dashboard.
Problem
Tests in spreadsheets out of context — no idea what broke
- Scenarios in Notion, bugs in Jira, results in spreadsheets — three tools
- After a run it is unclear exactly what failed and why
- No history — no visibility into whether behavior is regressing
- No customization: someone else's tool built for someone else's process
How it works
How test management works
Create a project
Organise work by project — each project contains its own scenarios and checklists.
Add scenarios and steps
Record a scenario or create steps manually — the structure is hierarchical: project → scenario → steps.
Run a test run
Initiate a run for selected scenarios. Progon records the result of every step.
Analyse and track
Review run history, file bugs directly from results, monitor trends in the dashboard.
Capabilities
Full QA toolkit
Hierarchy: project → scenario → steps
Structured workspace without unnecessary nesting. Multiple teams — multiple projects. Scenarios logically grouped.
Test runs and history
Every run saves the status of each step and scenario. History is always accessible — see exactly when a regression appeared.
Bug tracking
A failed step — one button to "File a bug". The bug is linked to the scenario, run and step. No separate Jira ticket with manual context copying.
Manual checklists
Create checklists for exploratory testing directly on product pages. Check items in context, not in a separate tab.
Custom fields and dashboard
Add fields to match your process: priority, assignee, environment. The dashboard shows the big picture across projects and teams.