Solution · Recording & Playback
Record the path once — Progon runs it every time
Record user actions directly in the browser. Progon replays the scenario in manual, semi-automatic or fully automatic mode — steps are bound to real DOM elements and survive UI redesigns.
Manual retesting after every deploy — hours of wasted work
Without Progon: The same user path is clicked manually over and over
With Progon: Record once — run with one click
Without Progon: Layout changed — the test script broke
With Progon: Self-healing selectors survive redesigns
Without Progon: Regressions are found by users, not QA
With Progon: Regressions are caught before release
From recording to automated run
Record the path
Click through the scenario in the browser — every action is captured automatically.
Steps are bound to DOM
Each step is linked to a real page element through a set of resilient selectors.
Choose your mode
Manual — system guides you; semi-auto — step by step; auto — the whole scenario.
Run without limits
Run the scenario as many times as you need, track history and statuses.
Capabilities
What is included
In-browser action recording
Clicks, text input, navigation and waits are captured without a single line of code. Just open the page and click through — the extension does the rest.
DOM element binding
Each step is bound to a real element by multiple signals: id, aria-label, text, CSS path. One signal disappears — Progon uses another.
Self-healing selectors
Layout changed — Progon re-locates the element and continues the run. A renamed class or shifted div does not break the test.
Three playback modes
Manual: user acts — system detects. Semi-auto: system prompts each step. Auto: scenario runs fully hands-free.
Unlimited runs
No limit on the number of runs. Run scenarios after every deploy, catch regressions before release.