Manual tester
There is no language, framework, or build system to learn. Build the regression flow you run manually every release once, then launch it in two clicks.
No-code automated tests with no infrastructure
Build a scenario from steps or turn an existing test case into an automated test with the AI assistant. Runs execute in browsers on our infrastructure. There is no CI/CD pipeline, server, or framework for you to maintain.
- Chromium, Firefox, WebKit
- Mobile User-Agent
- Up to 10 parallel workers
- Run screenshots
- No CI/CD or own servers
Automation no longer requires an automation engineer
The same product covers three different situations within a team.
QA lead of a small team
There is no need to assign someone to maintain a framework. Runs execute in parallel, while steps and locators stay in a shared catalog rather than somebody else's repository.
Team without its own environment
You do not need runners, images, or a CI/CD queue. We provide the browsers and run resources, while reports remain in your project.
Four steps to your first run
From an empty project to a result in the browser. Nothing needs to be installed.
- 01
Connect a domain
Add and verify the domain of your environment. Automated tests run only against domains verified by your team. Tests cannot be launched against third-party sites.
- 02
Build a scenario
A step contains an action, target, and value: open, click, fill, or verify. Alternatively, give a test case to the AI assistant and receive ready-made steps.
- 03
Start the run
Choose a browser, resolution, worker count, and retry count. The run enters the queue and executes on our side.
- 04
Review the result
You can see the exact step where the scenario stopped. A failure screenshot is captured by default, and a final screenshot can be enabled.
Turn a test case or defect into an automated test
The AI assistant builds a ready-to-use prompt from your test case, page, or defect. Run it in the model of your choice, then import the result back into the project. Imported scenarios receive a tag so you can review and edit them before they run.
Defects have their own workflow. A fix described only in words can regress. An automated test built from reproduction steps remains in the project and catches the regression in the next release.
Change a locator in one place
Pages and elements live in separate catalogs. In each step, you select an element from the catalog instead of entering a selector manually. When the interface changes, update one record instead of twenty steps across ten scenarios.
Move a repeated scenario opening into a shared block and connect it as a precondition. It runs in the same browser session before the main steps.
Usernames and passwords come from project test accounts instead of being stored as plain text in a step.
Pages
Sign in
/loginProject list
/projectsTest case page
/test-case/:idElements
Sign in button
role = buttonLogin field
name = loginProject row
testid = project-rowBrowsers, resolutions, and parallel execution
Runs use Playwright browser engines from our image. Configure the settings in the run form.
- Browsers
- Chromium, Firefox, WebKit, headless Chromium
- Resolutions
- Any active system resolution
- Mobile checks
- Mobile User-Agent, resolution, and touch capabilities
- Parallel execution
- Up to 10 workers in one run
- Retries
- Up to 3 retries for a failed scenario
- Timeouts
- Separate limits for a step, scenario, and run
- Stopping
- After a configured number of consecutive errors
- Screenshots
- Failure and final screenshots
A phone is reproduced through its User-Agent and screen resolution: the site serves its mobile layout, while the worker supplies mobile and touch capabilities. A Playwright device profile is not applied, so Chromium with a mobile User-Agent remains Chromium.
What works now and what comes next
Available now
- Web interface actions and assertions
- Page and element catalogs
- Preconditions and test accounts
- Parallel runs and retries
- Failure and final-step screenshots
- Scenario import through the AI assistant
- Mobile User-Agent and touch capabilities
Planned
- More browsers
- API testing
- Screenshot comparison
- An environment for running your Playwright tests
- A browser extension for recording tests
Our documentation describes what the product supports in a specific version and does not promise capabilities that are not available.
Frequently asked questions
Do I need programming skills?
No. You build a scenario from steps in the interface. Playwright knowledge can help you understand the underlying process, but it is not required.
Do I need my own server or CI/CD pipeline?
No. Runs execute on our infrastructure, so there is nothing for you to install or maintain.
Can I run tests against somebody else's site?
No. Tests run only against domains verified by your team. This restriction is intentional.
What happens to scenarios when the interface changes?
If locators come from the element catalog, update one catalog record instead of every step.
Is our data sent to a language model?
Only if you send it yourself. We do not run a model or submit the prompt for you.
Can I transfer scenarios from another system?
Yes. Import a JSON array containing up to fifty scenarios at a time.
Build your first automated test today
One domain, ten steps, one run. Then it works for you with every release.
Contact form
Leave a request and we will get in touch to discuss your team’s needs and find the right solution.
Tailored to your workflow
We do not only sell a ready-made product — we adapt the platform to real processes and requests. Tell us what matters to you.
Personal demo
Book a personal ComplexQA demo for you and your QA team. We will show how the platform solves typical tasks.
We are open to conversation
Questions, ideas, or feedback? Write to us at support@complexqa.com or fill in the form.