Regressions reach users unnoticed
Manual passes only cover what someone remembered to click. A broken flow, a shifted layout or a failing request can ship without anyone noticing.
Public paid beta: 100 signup credits included · shared pool or local Docker runner
Learn moreQalizer is in a paid public beta. Paid credit packs are available. Features, limits and the interface can still change, runs can be queued or delayed, and AI-generated content is advisory — every single limitation is listed in the capability summary below. Signup credits are granted when your account is created.
Paid public beta prepaid credits
Qalizer crawls your site, generates and records browser scenarios, and runs API, liveness, visual, console/network, load and monkey tests — on the shared server pool or on your own runner — with reports and CI artifacts on a pay-per-action credit model.
$ qalizer run --url https://your-site.dev --mode deterministic --set checkout
Manual passes only cover what someone remembered to click. A recorded or generated scenario can be re-run on every release instead.
Manual passes only cover what someone remembered to click. A broken flow, a shifted layout or a failing request can ship without anyone noticing.
Re-clicking the same flows before every release costs the same hours each time. Recorded and generated scenarios can be re-run instead.
Crawl → generate → record → run → report. Browser scenarios run on a schedule or from CI; the dedicated test families are started individually.
Every capability, how it can be started and where it runs is listed in the capability summary below. Anything not listed there is not supported.
Discover pages with FastCrawl, DeterministicPass or DeepCrawl modes and build a DOM tree and sitemap with complexity-based pricing. How much of the site is reached depends on the mode, depth and page limit you set.
From crawled pages, AI proposes positive, negative and edge-case scenarios. Classification (auth, forms, purchase, navigation) steers generation. Generated scenarios are proposals: review them before you schedule a run.
Record browser flows with the Qalizer Chrome extension or the in-app recorder, review the captured steps, then promote, schedule and run them. Replay can heal a broken selector; healing is best-effort, not a promise that every change is repaired.
Get the Chrome extensionGroup browser scenarios into sets and run them together as “Run All”, with optional AI verification and completion emails. Sets can be scheduled and triggered from CI; the dedicated test families cannot join a set.
Auto-generate or CSV-upload test data and inject it into form fields, replacing recorded values with fresh values per row. Run it against an environment where writing test data is allowed.
Monkey testing with configurable intensity and duration. Random interaction can find crashes a scripted test misses — and it can also create, change or delete data in the target, so use it only where side effects are acceptable.
Baseline screenshots and pixel diffs, with dynamic-content masking to reduce false positives. Differences caused by animation, fonts or videos can still be flagged, so review each diff.
HTTP health checks on pages and endpoints, run on demand or on a schedule, with status and latency recorded per check. A check needs a reachable target with credentials the environment accepts.
Generate concurrent load with a configurable concurrency and duration and read latency/throughput results. Capacity is bounded by the shared pool, so run it against an environment that can absorb the load.
Discover endpoints from OpenAPI/Swagger or define them by hand, then check status, latency and response shape. API checks run individually or in “Run All”, and in CI only after promotion to a browser scenario.
Capture console messages and network failures per page and surface JavaScript exceptions and failing requests that a passing scenario can hide.
Failed runs create an issue with the failed step and its screenshots, plus an AI-generated summary that is advisory and may be incomplete.
HTML, PDF, JSON and JUnit run reports with steps, screenshots and logs. Completed artifacts are kept for 180 days after the run finishes, so export what you need.
API tokens and CI runs with exit codes for pipelines. The JUnit document is the gate: a run is green only if it parses and contains no failure, error or skipped element.
Upload requirement documents and let AI analyse them, then trace generated tests back to requirements. AI matching is advisory — review the coverage list before relying on it.
Run browser scenarios on your own machine with a Docker-based runner, for apps only your network can reach. Execution happens on your hardware; the selected results and artifacts are uploaded to and retained on Qalizer.
In-app notifications and a live execution queue show when a run finishes or fails while you are on the page. Email notifications are sent for completed runs, and scheduling can also include them.
Pay per action — crawl, run or test. Every account receives 100 signup credits when it is created. No subscriptions and no per-seat minimums; top up when you need more.
Five steps, each one visible in the product. Your results stay reviewable at every stage.
Register with an email address. The 100 signup credits are granted at signup, before you create anything — no credit card needed to start.
/registerEnter the URL of a site you own or are authorised to test, then choose FastCrawl, DeterministicPass or DeepCrawl. The crawl maps the DOM tree and sitemap within the depth and page limits you set.
crawlLet AI propose positive, negative and edge-case scenarios from the crawl, or record flows yourself. Review and adjust them before anything runs on a schedule.
ai · recorderRun one scenario, “Run All” over a scenario set, a schedule, or CI — on the shared server pool or your own runner. API, liveness, visual, console/network, load, gremlins and data-injection tests are started individually.
5 entry pointsOpen the report with every step, screenshot and capture. Artifacts are kept for 180 days after the run finishes, so download anything you need to keep.
html · json · junitEvery action has a credit cost that is shown before you start it — from a single API check to a full crawl. A new account receives 100 signup credits at signup; further credits are bought in prepaid packs. Prices can change during the beta.
Each action, from a crawl to a single API check, has a fixed credit cost that the product shows before it runs. Your balance and usage history are visible at any time.
100 credits are added to the account when you register. They are usage credits, not cash, and no credit card is needed to register.
There is no free plan; usage beyond signup credits is prepaid.
Register, point Qalizer at a site you are authorised to test, and see what the crawl finds. The beta is a paid service with documented limits — nothing here is a promise of a defect-free release.