Overview

QAClan records what you click and turns it into a test that runs again tomorrow. It runs on your machine; sharing the results with a team is optional.

Runs on: Your machine, at localhost:7823
Costs: The agent is free. Sharing is the Team plan
Needs: No coding, no Node, no Python

How it fits together

on your machine

Web testing

Record a browser journey. You get a real script you can open and edit.

API testing

Capture the calls behind that journey, or import from Postman, Bruno or a HAR file.

Suite

Recorded scripts and API requests as one ordered list, run back to back in a shared session.

Run

Pass or fail for every item, with a screenshot, a plain-language reason and logs for whatever failed.

results sync · optional

qaclan.com

Run history across machines, six regression reports, and a workspace your teammates share.

Browser tests and API tests are not two products here — they meet in the same suite and the same run, so one result covers both. Everything inside the dashed outline happens on your own machine, which is why your application never has to be reachable from the internet. Log in and every machine on the team feeds the same workspace.

The agent is a single command called qaclan, running on your own machine. It records browser journeys, captures or imports the API requests behind them, runs everything and keeps it all in ~/.qaclan/. It has its own app at localhost:7823, it works offline, and it is free.

The server is qaclan.com. Log in and the agent syncs your work to a shared workspace, which adds run history across machines, regression reports, AI script analysis and team seats. The agent is always required; the server is not.

Start here

If you want to	Go to
Get a first test passing, having never used this	Getting started
Understand a screen or an option in front of you	The local app
Test the API behind a journey, not just the browser	API testing
Run this in CI, or script it	CLI reference

The words these pages use

Nothing below assumes a term you have not met yet, so it reads top to bottom.

Term	What it means
Project	One application you are testing. You work in one at a time.
Feature	A folder inside a project for one area of it — checkout, login, search.
Script	One recorded browser journey, saved as a real Playwright file you can open and edit.
Suite	An ordered list run back to back in one browser session, so a later item can rely on what an earlier one did — signing in, for instance.
Run	One execution of a suite and the result it produced: pass or fail per item, plus screenshots and logs for anything that failed.
Environment	A named set of variables — a base URL, a test account, a token — so the same suite can run against staging and production without editing it.
Collection	A group of saved HTTP requests, optionally arranged into folders.
Request	One saved HTTP call — method, URL, headers, body, and the checks that should pass when it runs.
Case	A deliberately wrong version of a request, generated so you can check the API rejects it properly. See negative testing.
Drift	A response whose shape no longer matches the shape you froze earlier — a field gone, or a type changed. See schema drift.

How these pages are written

QAClan is used through the app on your own machine — pointing, clicking and reading results. That is how every page describes it, and no step anywhere requires you to write code.

Every action also has a command, for CI or for scripting something repetitive. Those sit underneath the app instructions in a Prefer the terminal? section you can open when you want it. The complete list is the CLI reference.

Reference material that you do not need in order to finish a task is folded into sections like this one. It is still searchable — your browser’s find will open it.

Coming from docs.qaclan.com?

The documentation used to live on a second site as one long page with numbered sections. That address now redirects here. Because the old sections were page anchors, a bookmark to one lands on this overview rather than the section itself — here is where each went.

Old section	Now on
01 Overview · 03 Core Concepts	This page
02 Quick Start · 05 Authentication	Getting started
04 Installation	Install and setup
06 Tour · 07 Projects · 08 Features	The local app
09 Scripts	Web testing
10 Suites · 11 Running Tests	Suites, runs and reports
12 Environments	Environments and secrets
13 Cloud Sync	Sync, team and plans
14 Reports & Analytics · 15 Team Collaboration	The cloud workspace
16 CLI Reference	CLI reference
17 Pricing	Pricing