Engineering
Overnight UI QA: spec bot, test bot, email bot
UI regressions wait for a human QA pass that never starts.
What hurt
Steven Bowler (ex QA engineer) named automated UI testing as his best Grok Bot use case. One bot links the repo and writes the UI test spec. A second QA bot ingests that spec and runs the test script. A nightly timer fires it. Results hand off to an email bot. No published system prompt — steal the three-bot split and the schedule.
What to install or create
Three bots, one handoff chain. Spec bot owns the repo-linked UI spec. QA bot only runs what the spec says. Email bot only sends the report. Hang the QA run on a nightly routine. Keep send gated.
Bots
Spec writer
Links the repo and drafts the UI test spec. Does not run tests.
QA runner
Ingests the UI spec, runs the test script on schedule, writes a report.
Email handoff
Sends the nightly report only after your send rules allow it.
Plugins
Browser
Optional
Files
UI test spec file in the repo. Nightly report note.
Routines
Nightly: wake QA runner, run the suite, hand the report to email bot.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Create a Spec writer bot. Point it at your app repo. Ask it to draft a UI test spec only — no inventing a framework the tweet never named.
- 2Create a QA runner bot. Its job is ingest the spec and run the matching test script.
- 3Create an email handoff bot (or lane) that only sends the report. Gate send.
- 4Hang the QA run on a nightly routine. Watch one dry run before you leave it on.
- 5First live email and any repo write need your yes.
Approval fence
Emailing results or writing into the repo needs your yes the first time. Nightly runs stay read/report until you say otherwise.
What to tweak
Steal the pipeline: write spec → run tests on a timer → email results. Do not invent a Playwright prompt the author never posted.
Source
Delta Solutions AI @DeltaSolutionAI · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.