Qalizer 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.
Automate your web QA.
Crawl, generate, run and report — with AI in the loop.
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.
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.
Manual regression takes hours
Re-clicking the same flows before every release costs the same hours each time. Recorded and generated scenarios can be re-run instead.
One workflow, one place
Crawl → generate → record → run → report. Browser scenarios run on a schedule or from CI; the dedicated test families are started individually.
Eight test families
What Qalizer actually runs
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.
DOM Tree & Sitemap Crawling
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.
Auto Test — AI-Generated Tests
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.
Scenario Recorder
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 extension →Scenario Sets & Scheduling
Group 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.
Data Injection
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.
Gremlins Chaos Testing
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.
Visual Regression
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.
Liveness Monitoring
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.
Load Testing
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.
API Testing
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.
Console & Network Log Capture
Capture console messages and network failures per page and surface JavaScript exceptions and failing requests that a passing scenario can hide.
Bug Reports
Failed runs create an issue with the failed step and its screenshots, plus an AI-generated summary that is advisory and may be incomplete.
Reports — HTML + JSON
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.
CI/CD Integration
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.
Requirements & Traceability
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.
Local Runner
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.
Real-Time Notifications & Queue
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.
Credit-Based Pricing
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.
From URL to report
How the beta workflow works
Five steps, each one visible in the product. Your results stay reviewable at every stage.
Create an account
Register with an email address. The 100 signup credits are granted at signup, before you create anything — no credit card needed to start.
Add a monitor
Enter 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.
Generate or record tests
Let 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.
Run it your way
Run 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.
Read the evidence
Open 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.
Usage-based, prepaid
Credits you buy and spend. No subscription.
Every 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.
How Credits Work
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.
View Credit Costs →100 Signup Credits
100 credits are added to the account when you register. They are usage credits, not cash, and no credit card is needed to register.
Create a beta account →FAQ