gitwtfhub

wtf is ai-qa-pipeline?

vladyslavdmitriiev/ai-qa-pipeline — explained in plain English

Analysis updated 2026-05-18

1TypeScriptAudience · developerComplexity · 3/5Setup · moderate

TL;DR

Turn plain-English feature descriptions into reliable Playwright tests through a multi-agent review pipeline. Each stage is checked by a different AI model to prevent self-approval bias.

Mindmap

mindmap
  root((repo))
    What it does
      Generates Playwright tests
      Multi-agent review pipeline
      Cross-model quality checks
    How it works
      Parser validates input
      Feature Reviewer agent
      Test Writer agent
      Spec Judge agent
    Quality gates
      Mutation testing gate
      Debug Agent for fixes
      No self-approval rule
    Tech stack
      TypeScript
      Playwright
      Node 20
      Claude Code CLI
    Use cases
      Demo shop included
      Local pipeline testing
    Audience
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Write a plain-English feature spec and get ready-to-run Playwright tests generated and reviewed automatically.

REASON 2

Run the included demo shop to see the full multi-agent test generation pipeline in action locally.

REASON 3

Add a quality gate to your test suite that uses cross-model AI review to catch weak or passing-by-default assertions.

REASON 4

Generate tests that only use real element selectors from your app's source code, avoiding invented selectors.

What's in the stack?

TypeScriptPlaywrightNode 20Claude Code CLI

How it stacks up

vladyslavdmitriiev/ai-qa-pipeline0xkinno/neuralvault0xmayurrr/ai-contractauditor
Stars111
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardeasy
Complexity3/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires Node 20 and the Claude Code CLI to be installed locally.

Wtf does this do

This project turns plain-language feature descriptions into automated tests you can actually trust. You write a short description of what a feature should do, and the system produces Playwright tests that check your app against that description. The tests go through multiple stages of review before they are accepted. The core principle is that no agent in the pipeline gets to declare its own work done. A parser checks the feature file before any AI model is called, and it rejects structurally broken inputs for free. Then a Feature Reviewer agent checks whether a test writer could implement the spec without guessing at details. It rejects scenarios that are vague or contradictory, but it does not reject based on style or missing edge cases. A Test Writer agent then drafts the actual test code. It can only use element identifiers that already exist in your app's source code, which prevents it from inventing selectors that would never match anything. A Spec Judge running on a different AI model reviews the draft before it ever runs. Using a different model matters because a judge from the same model family tends to excuse the writer's own patterns. The judge checks that every scenario is present, every assertion can actually fail, and no meaning was weakened. If the judge approves, the test runs for real against the app. If it fails, a Debug Agent may fix mechanical problems like locators or timing, but it is not allowed to change what the test asserts. After debugging, the spec goes back to the judge one more time to confirm nothing was quietly weakened just to make it pass. A mutation gate then runs as a final check on the frozen baseline. The project includes a demo shop so you can try the whole pipeline locally. You need Node 20 and the Claude Code CLI installed. The full README is longer than what was shown.

Yoink these prompts

Prompt 1
I have a feature description for my web app. Can you help me structure it so the ai-qa-pipeline Feature Reviewer agent will accept it without rejecting it for being vague or contradictory?
Prompt 2
Help me set up the ai-qa-pipeline locally with Node 20 and Claude Code CLI, and walk me through running the demo shop to see test generation in action.
Prompt 3
The Spec Judge in ai-qa-pipeline rejected my generated tests because assertions could not actually fail. Can you review my Playwright test draft and flag assertions that always pass no matter what?
Prompt 4
My ai-qa-pipeline generated test failed during the real run. How do I use the Debug Agent to fix locator and timing issues without changing what the test asserts?
Prompt 5
Help me understand how the cross-model Spec Judge works in ai-qa-pipeline and why using a different AI model family for judging prevents the writer model from excusing its own patterns.

Frequently asked questions

wtf is ai-qa-pipeline?

Turn plain-English feature descriptions into reliable Playwright tests through a multi-agent review pipeline. Each stage is checked by a different AI model to prevent self-approval bias.

What language is ai-qa-pipeline written in?

Mainly TypeScript. The stack also includes TypeScript, Playwright, Node 20.

How hard is ai-qa-pipeline to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is ai-qa-pipeline for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.