QA Web Agent

How a change flows from signal to shipped.

Seven stages, one queue, one set of workers. Every stage leaves evidence, and every stage where judgement matters waits for a person.

The seven stages.

The dashboard's Home canvas: the traditional QA lifecycle mapped stage by stage to what the platform automates today.

  1. A signal arrives

    A pull request is opened or pushed, an issue is watched, a schedule fires, a signed webhook lands, or a person clicks Run. Every signal becomes jobs on one durable queue with leases and a visibility timeout.

  2. The environment comes up

    If the project declares one, a fresh copy of the app is built from the exact commit in a private namespace, patched, seeded with data and health-checked. Otherwise the run targets the configured URL.

  3. The agent runs the tests

    Plain-language tests, a real browser, prerequisites resolved from the catalog, screenshots and video captured as it goes, one forced retry before any failing verdict.

  4. The verdict is posted

    A label and one updating comment on the pull request, a retest comment on the issue, a Slack card, a webhook, a live event stream and the dashboard. Same payload everywhere.

  5. Findings become work

    A failed run becomes a filed bug with steps and video. An exploration finding becomes a regression test. A confirmed bug can be assigned to the code agent.

  6. The fix is proven and handed over

    The agent edits on an internal git host, boots the app from its branch, runs the proving test on a fresh environment, and a reviewer graduates the change into a real pull request, which is then watched like any other.

  7. The documents follow

    Merged pull requests update the requirements suite, contradictions become conflicts for a person, and the day's changelog is drafted behind a publish gate.

Test your site on your own machine.

The IsNull deployment starts with the private isnull-site repository as its project. The API, database and document worker run on the VPS. A connected qawa-node clones the site and starts its Astro preview in a temporary Docker container on your machine when a test needs an isolated environment.

You can write tests for the site's pages and run jobs from multiple connected nodes. The deployment seeds the project and its GitHub access; it does not add sample tests or demo projects.

What the IsNull deployment seeds
project:  isnull-site
source:   IsNullSoftworks/isnull-site (private, main)
worker:   qawa-node on a connected user machine
site:     Astro on port 4321 in a temporary Docker box
tests:    authored in the platform; no demo tests

Three services, one queue.

The API and document worker share a durable MongoDB queue on the IsNull VPS. Browser test workers run in Docker on user machines through qawa-node, and several nodes can run jobs in parallel. An infrastructure-blocked job is retried once as a fresh job; a job's scratch is removed when it ends and swept at boot. Ansible applies reviewed k3s manifests to the VPS.

The Workers view: worker instances, their concurrency and the jobs they are running.