Scenario

Record once. Catch every break, forever.

Click through a login, checkout, or sign-up in a real browser - TestCLIX records every step and replays it on a schedule. When something fails, you get a full replay in the Session Player, not just an error code.

  • No code or framework setup
  • Every scenario runs on its own schedule
  • Screenshots & full event log on every run

Codeless Recorder

No code. No plugin. Just click.

The Codeless Recorder streams a real browser session to your screen - you click, type, and navigate as you normally would. Every interaction is captured as a repeatable step. No Selenium, no Playwright config, no script to maintain.

  • Captures clicks, form fills, navigation, and page-state changes
  • Works for business owners, product managers, and marketing teams - not just QA
  • Steps are stored and editable after recording
  • Trigger manually or schedule immediately after recording

SCHEDULING

Pick how often. We'll handle the rest.

Choose a schedule that matches the risk level of the flow - a checkout needs to run every few minutes; a less critical form can run hourly.

Available frequencies

Frequency Runs / day Best for
Every 5min 288×Mission-critical flows
Every 10min 144×Key checkout / login
Every 15min 96×Core user flows
Every 1h 24×Secondary flows
Every 6h Low-risk validation
Every 24h End-of-day sanity check
Do not schedule On-demandManual / CI triggers

Live schedule preview

Today Tue · Jul 28

Live

Live schedule for Tue · Jul 28, running every 5min. 138 passed and 4 failed of 142 checks run so far today. Next check at 11:50.

Pass Error

142 / 288 today · next

Session Player

When a test fails, see exactly what the user saw

Every run is captured step by step: timeline, screenshots, and DOM context. Compare against a baseline with visual masks, run the image and movie checkers, or ask the AI assistant about a selected region of the screen.

  • Event timeline & screenshots - scrub to any step and see the rendered page.
  • Comparison masks & checkers - image and movie diffing against your baseline.
  • AI assistant on a screen region - select an area and get a failure explanation in context.

Pixel Comparison

Catch visual regressions pixel by pixel.

Every step in a scenario can be compared against the original screenshot at pixel level. If anything looks different - a shifted button, a missing element, a layout change - the test fails and you see exactly where.

  • Full-screen pixel-by-pixel comparison between original and current run
  • Ignored Zones - draw rectangles to exclude ads, chat widgets, or dynamic content from comparison
  • Failure message: "Step N: Unable to execute step: The image check failed"

Locations

Run scenario tests from the regions that matter to your users

Multi-step user flows can behave differently depending on where they're accessed from. Each scenario runs from a single location you choose - create one scenario per region to compare and catch geography-specific issues.

  • Five regions available - four in Europe, one in North America, with more by request.
  • One location per scenario, set when you create it or from Edit test properties afterward - every step in the flow runs from that same location
  • Duplicate a scenario to a second region to catch location-specific regressions in the user flow

Alarms & Notifications

Alerting that matches your risk tolerance

Every scenario test evaluates its own recent run history: set how many runs to look at and how many failures should trip the alarm. A higher failures-to-alarm threshold filters out one-off blips - like a flaky network - so you're only alerted about real regressions.

  • Evaluation period & failures to alarm - both configurable from 1 to 50 runs, independently per test.
  • Notify by email, Slack, Telegram, Jira or webhooks - with a screenshot and the failing step attached
  • Reduces false alarms from temporary issues like network instability, so you're only notified about real regressions
Evaluation period:
5 runs
Failures to alarm:
2 runs

Recent runs

Pass Error

When 2 failures are reached, notify via:

Recorder feature

Everything the recorder captures - and verifies

Actions capture what your users do. Checkers confirm every scheduled run still looks and behaves the same.

Actions - what it records

Everything you do in the browser becomes a step

  • Mouse clicks - every click on a link, button, or menu replays on exactly the same target.
  • Typing & special keys - form fills, Tab, Enter, and Escape replay exactly as your users type them.
  • Clipboard paste - pasted codes and tokens are captured as their own step.
  • Back & forward - flows that rely on browser history replay faithfully.
  • Scrolling - the right content is in view at the right moment.
  • Wait steps - add a pause where a page needs time to load or settle.
  • SSO logins - redirect-based sign-in flows are recorded end to end.
  • Masked fields - passwords never appear in screenshots or stored step data.
  • Step screenshots - visual proof captured at every single step.
Explore the Codeless Recorder docs

Checkers - what it verifies

Every scheduled run is checked, not just replayed

  • AI failure explanation - a plain-language answer to what likely broke - no log digging.
  • Full-page pixel compare - flags any visual difference across the whole page.
  • Screen fragment compare - watches one key area - a price, a button, a banner.
  • Movie checker - confirms embedded video actually starts and plays.

Checkers run automatically on every scheduled replay - when one fails, the test flips to Error and you get the failing step, a screenshot, and an alert.

See how checkers work

FAQ

Frequently asked questions

Record your first scenario in under 5 minutes

No setup, no framework, no code. Just open a browser and click through your site.