towlar.
EN/TR

Coming soon

QA OS

A local-first AI test cockpit for planning, generating and running UI and API tests.

QaOs — Test Cockpit

One cockpit for planning, automating and running UI and API tests. The capabilities below are available in preview; the next section describes planned additions.

What you can do with QA OS

Available in preview

One cockpit

Plan, automate and run UI and API tests from a single workspace, with every case, run and change visible on one dashboard.

UI test cases from a live page

Describe a flow and point to a URL. QA OS walks the real page, including frames, shadow DOM and pop-ups, and writes Gherkin cases only from controls it actually found. Existing cases are reused as preconditions instead of being rewritten.

API cases from captured traffic

API requests recorded during a UI walk become API test cases in one click.

API test cases from any spec

Generate positive, negative, boundary and injection cases from OpenAPI, Postman, cURL, PDF or Excel. Each case comes with a ready cURL and the schema it asserts.

From cases to Playwright code

Selected cases become a Playwright TypeScript suite. The suite is run once to prove it really executes, and failures are reported as the product's answer, not hidden as flaky scripts.

Run, report, rerun

Run any folder against any environment, with consent for write requests. Every verdict carries its reason, and you can rerun only the failures.

Healing you approve

When a control changes, QA OS proposes the exact fix side by side. Nothing is written until you approve it, and approved fixes are verified in a separate run.

Write your own cases

Create cases by hand, reuse existing cases as preconditions, and validate structure and references before saving.

Same engine from the terminal

Every cockpit action is also a CLI command, and both give the same answer.

Local-first AI

Runs on local models through Ollama. Your code and data stay on your machine.

Coming next

Run & Record

Record a real browser session, then turn it into UI cases, API cases or a k6 / Gatling load test.

Knowledge Base

Versioned requirements and specs you can ask questions of, with cited answers and test plans tied to the exact source version.

PR Test Intelligence

When a pull request lands, QA OS maps the change to the tests that matter, runs them in the PR environment and reports on the merge check.

Connections

Connect GitHub, API specs and MCP tools such as Jira and Playwright once. Every new change then uses the same saved policy.

In development · Preview capabilities