Setting Up QA Agent
Read the guide below.
Turn this cable into a shipping system.
We help teams deploy reliable AI workflows with architecture, implementation, and hardening support.
Setting Up QA Agent
From zero to running your first automated browser test in 15 minutes.
What you'll learn
- How to clone and install QA Agent
- Which environment variables are required
- How to run the smoke test to confirm everything works
Prerequisites
- Python 3.11 or newer (
python3 --version) - Git
- An API key for at least one supported model provider (see Step 3)
Step 1: Clone the repository
git clone https://github.com/frenxt/qa-agent.git
cd qa-agent
Step 2: Create a virtual environment
Always use a venv to keep QA Agent's dependencies isolated from your system Python:
python3.11 -m venv .venv
source .venv/bin/activate # on Windows: .venv\Scripts\activate
pip install -e .
Step 3: Install the browser
QA Agent uses Chromium via browser-use. Install it once:
browser-use install
This downloads Chromium to a cache directory managed by Playwright. It takes a minute on a fresh machine.
Step 4: Set your API key
Copy the example env file:
cp .env.example .env
Open .env and set one of the following. QA Agent checks them in this order:
QA_LLM_API_KEY=sk-... # recommended: OpenRouter key (access to all models)
# OPENROUTER_API_KEY=sk-or-... # alternative: explicit OpenRouter key
# OPENAI_API_KEY=sk-... # fallback: direct OpenAI key
The default model is google/gemini-3.1-flash-lite-preview via OpenRouter. This is the model used across 480+ production spec runs — it balances speed and accuracy well for UI testing.
Step 5: Configure your base URL
Open config.yaml and set base_url to the URL of the product you want to test:
base_url: http://localhost:3000 # your local dev server
For a first run against a live site, you can point it at any public URL.
Step 6: Run the smoke test
python cli.py run --suite smoke
This runs the bundled smoke suite against your base_url. You should see output like:
Running suite: smoke
[1/2] Homepage loads ... PASS (12.3s)
[2/2] 404 page renders ... PASS (8.1s)
Report saved: reports/2026-04-17-smoke-01/index.html
Open the HTML report to see the full run with screenshots.
Troubleshooting
browser-use: command not found — run pip install -e . again inside your venv, then browser-use install.
API key not set error — confirm .env exists in the project root and has at least one of the three keys from Step 4.
base_url connection refused — start your local dev server first, then run QA Agent.
What's next
Quick answers
What do I get from this cable?
You get a step-by-step guide for this aspect of QA Agent.
How much time should I budget?
Typical effort is 15 min. The cable is marked beginner.
Do I need to know Python?
Basic familiarity with running Python CLI commands is enough for the user guide cables (1–5). The contributor guide (cables 6–7) assumes you can read and write Python.
How fresh is the guidance?
The cable was last verified on 2026-04-17.
More from @frenxt
How QA Agent Works (Architecture)
Before contributing, understand what runs when you type `python cli.py run --suite smoke`.
Contributing to QA Agent
QA Agent is open source. Contributions that add integrations, improve the report format, or extend the agent's tool set are all welcome.
Writing Your First Test Case
A good test case reads like a conversation between a QA engineer and a developer — not like code.