Settings
Keys are held in this process's memory only, and forgotten when it closes — unless you tick “remember in my keychain”, which puts them in your operating system's keychain so they come back after a restart or an update. Nothing is written to the project folder, so a new build cannot take them with it, and nothing leaves your machine except calls to the provider you configure.
Model providers
You need at least one. Without any, the agent falls back to a deterministic offline stub that cannot write usable test steps.
Which model does what
Seven jobs, each with its own model. Actor runs on every browser step and drives most of the cost; reasoning makes the judgement calls and deserves your best model. Saved to — configuration, never keys.
When to write cases
Before writing anything, the agent scores how testable a ticket is. Below this score the run stops and reports the requirement gaps instead — the questions for the Product Owner are the output. Lower it to get cases from a rough ticket; the gaps are still reported either way.
Where the test-case sheet goes
After a ticket is analysed, the sheet has to reach whoever asked for it.
Google needs a credential for every write — a folder id alone will not do. Signing in is the lighter of the two options: the sheet then belongs to you and nothing needs sharing.
Use a service account instead
For unattended runs on a server, where nobody is there to sign in. The sheet then belongs to the service account, so the destination folder must be shared with its email as Editor.
Integrations
Optional. ClickUp lets it read tickets directly instead of from a file.
Environments
The URL, the sign-in and anything else that differs between DEV, STG and PROD. Recording, replaying and reporting all take an environment, so the same script runs anywhere without the values being typed into it.
All environments
Tickets
Read a ticket, judge whether it is testable, and write the test cases. Its live output appears below as it runs.
Ticket to suite
Live output
Auto Machine
Give it a ticket. It writes the test cases, drives the app, keeps the scripts, runs them as a suite, and files what broke — the work you would otherwise do by hand, in that order.
UI/UX review of a page
No ticket needed. Give it a page and it opens a browser, looks at the page at phone, tablet and desktop widths, and reports what is wrong — with the evidence. The result is a run like any other: it streams to Live Logs, lands in Web Runs, and its failures can be filed.
What it will do
Live Logs
Today's runs, newest first. A run still going streams here as it happens. Earlier days are on the Runs tab.
Today
Scripts
Features group the recordings; the recordings are real Playwright specs, so each one runs in CI and on anyone's laptop unchanged.
All features
Scripts
Suites
A suite is a journey made of recordings — log in, search, filter, log out. Its scripts run in the order you put them in, in one browser session, so the login in the first is still a login in the last.
All suites
| Suite | Scripts | Last run | Actions |
|---|
Web Runs
Browser suite history. View replays the run's log exactly as it streamed; Report opens the per-case results with traces for the failures. API collection runs are under API Runs.
All runs
| Run ID | Suite | Status | Results | Started | Actions |
|---|
API Runs
Every API collection you have run, newest first. Open one to see each request it sent, the status it came back with and how its assertions did.
All API runs
| Run ID | Collection | Status | Results | Started | Actions |
|---|
Requests
Team
Who is in your organization, what they may do, and which projects they work on.
Organization
You are the site administrator, so you can work inside any organization. Pick one to manage its people — or create one, which is what every new customer starts with.
Team members
| Name | Role | Designation | Projects | Actions |
|---|
Open invitations
| Role | Expires | Actions |
|---|
Project access
A project with nobody ticked is open to everyone in the organization — that is how every project starts. Ticking people narrows it to them. Admins always see all of the organization's projects.
My profile
Your own details. Everyone in the organization can see your name and designation on the team list.
Basic information
Setup
What must be installed on this computer before you can record a script, replay one, or run a suite. Install the items marked required, then check the status below. Steps are for Windows, macOS and Linux.
Status on this computer
npm install run in the project folder.What you need
| Dependency | Needed for | Required | Version |
|---|---|---|---|
| Python | Running the app and Playwright | Yes | 3.10 or newer (3.12 recommended) |
| Project Python packages | The app's libraries (installed into .venv) | Yes | From requirements.txt |
| Google Chrome, or Playwright's Chromium | Opening the browser to record and run scripts | Yes | Chrome: current stable |
| Node.js (with npm and npx) | Replaying scripts and running suites | Yes, for replay | 20 LTS or newer |
| MySQL or MariaDB | Shared database, instead of the local SQLite file | Optional | MariaDB 10.4 or newer, MySQL 8 |
libsecret (secret-tool) | Saving keys in the system keychain on Linux | Optional | Any |
Windows
- Python 3.12. Download the Windows installer from
python.org/downloads/windows.
On the first screen tick Add python.exe to PATH, then click Install Now.
Check it in a new Command Prompt:
python --version. - Google Chrome. Download from google.com/chrome and run the installer. The recorder finds it automatically; no extra browser download is needed.
- Node.js LTS. Download the Windows installer from
nodejs.org, keep the default options, and finish.
Check:
node --versionandnpm --version. - Project packages. In the project folder, run the commands in
Install the project below. Then run
npm installonce in the project folder. - MySQL or MariaDB (optional). Install
XAMPP (includes MariaDB), start MySQL
in the XAMPP control panel, and set
SQA_DATABASE_URLin.env.
macOS
- Python 3.12. Download the macOS installer from
python.org/downloads/macos
and run it, or with Homebrew:
brew install python@3.12. Check:python3 --version. - Google Chrome. Download from google.com/chrome and drag it into Applications. The recorder finds it automatically; no extra browser download is needed.
- Node.js LTS. Download the macOS installer from
nodejs.org, or with Homebrew:
brew install node. Check:node --version. - Project packages. Run the commands in Install the project below, then
npm installin the project folder. - MySQL or MariaDB (optional).
brew install mariadb, thenbrew services start mariadb. SetSQA_DATABASE_URLin.env.
Linux (Ubuntu / Debian)
- Python 3.12 with venv.
sudo apt update && sudo apt install python3 python3-venv python3-pip. Check:python3 --version. - Browser. Google Chrome from
google.com/chrome (the recorder
does not detect Chrome on Linux yet), or Playwright's Chromium (about 150 MB), installed in the
Install the project steps. On Linux also run
python -m playwright install-deps chromiumonce to install the system libraries it needs. - Node.js LTS. Use the NodeSource packages from
nodejs.org/en/download, or
sudo apt install nodejs npmif your release is 20 or newer. Check:node --version. - Project packages. Run the commands in Install the project below, then
npm installin the project folder. - Optional. MariaDB:
sudo apt install mariadb-server. System keychain:sudo apt install libsecret-tools.
Install the project
Run these from the project folder. Windows commands in Command Prompt.
python -m venv .venv .venv\Scripts\python.exe -m pip install -r requirements.txt .venv\Scripts\python.exe -m pip install -e . npm install .venv\Scripts\python.exe -m playwright install chromium # only if Chrome is not installed
python3 -m venv .venv .venv/bin/python -m pip install -r requirements.txt .venv/bin/python -m pip install -e . npm install .venv/bin/python -m playwright install chromium # only if Chrome is not installed python -m playwright install-deps chromium # Linux only, once
Start the app
Windows (Command Prompt):
set "PYTHONUTF8=1" && set "PYTHONPATH=packages/core" && .venv\Scripts\python.exe -m sqa_core ui --port 8765
macOS and Linux:
PYTHONUTF8=1 PYTHONPATH=packages/core .venv/bin/python -m sqa_core ui --port 8765
Then open http://127.0.0.1:8765/. Refresh this page
after installing something to update the status above.
API
Record your app once and keep the calls it makes. A collection is a folder of requests inside this project — recorded from a browser, or added by hand.