QualityMax

September 12, 2026 · View on GitHub

 ██████╗ ██╗   ██╗ █████╗ ██╗     ██╗████████╗██╗   ██╗███╗   ███╗ █████╗ ██╗  ██╗
██╔═══██╗██║   ██║██╔══██╗██║     ██║╚══██╔══╝╚██╗ ██╔╝████╗ ████║██╔══██╗╚██╗██╔╝
██║   ██║██║   ██║███████║██║     ██║   ██║    ╚████╔╝ ██╔████╔██║███████║ ╚███╔╝     ╱|、
██║▄▄ ██║██║   ██║██╔══██║██║     ██║   ██║     ╚██╔╝  ██║╚██╔╝██║██╔══██║ ██╔██╗    (˚ˎ 。7
╚██████╔╝╚██████╔╝██║  ██║███████╗██║   ██║      ██║   ██║ ╚═╝ ██║██║  ██║██╔╝ ██╗    |、˜〵
 ╚══▀▀═╝  ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝   ╚═╝      ╚═╝   ╚═╝     ╚═╝╚═╝  ╚═╝╚═╝  ╚═╝    じしˍ,)ノ

QualityMax

Independent verification for AI-written code.

Discover user journeys, generate and run tests, review changes, and inspect the evidence behind your next release.

Website · Open QualityMax · Documentation · Standalone tools

This repository is the public product guide and documentation entry point. The hosted platform source is maintained separately. Individual tools below have their own source repositories, licenses, and requirements.

Choose your starting point

I want to…Start here
Generate coverage and inspect a first completed runWeb app quickstart
Connect my coding agent to hosted QualityMaxMCP quickstart
Use the platform CLI and local execution agentCLI quickstart
Try local tools without a QualityMax accountStandalone tools guide
Evaluate QualityMax for my teamTeam evaluator guide

Hosted workflows require a QualityMax account and use the allowances of your plan. Standalone tools have separate prerequisites; model providers, coding-agent subscriptions, and your own compute can have costs.

From a user journey to reviewable evidence

┌─ FROM JOURNEY TO EVIDENCE ───────────────────────────────┐
│                                                          │
│   01  DISCOVER    Map application journeys               │
│        │                                                 │
│   02  GENERATE    Create cases and scripts               │
│        │                                                 │
│   03  REVIEW      Check intent and assertions            │
│        │                                                 │
│   04  EXECUTE     Run the reviewed tests                 │
│        │                                                 │
│   05  INSPECT     Read results and available artifacts   │
│        │                                                 │
│   06  REFINE      Review repairs if needed; rerun        │
│        │                                                 │
│        └────────> Retain the evidence                    │
│                                                          │
└──────────────────────────────────────────────────────────┘

QualityMax organizes work as Projects → Test Cases → Automation Scripts. A test case records expected behavior; scripts implement that intent for a framework. Inspect the completed execution and its available artifacts before treating a queued job or a generated script as proof. Core concepts

Explore the platform

CapabilityWhat to expectDocumentation
Discovery and generationDiscover application journeys and produce reviewable cases and scriptsDiscovery & Generation
PR verificationReview changes, run supported suites, and check deployed previewsCode Review & Gates
NexusSpecialist reviews with attributed findings and shareable reportsNexus review
AI application validationConversation evaluation, adversarial evaluations, and hallucination checksAI validation
Agentic EyesSimulated browser journeys with observations about usability and frictionAgentic Eyes
Self-healingInvestigate failed tests and review proposed repairsSelf-healing
SlackProject-aware questions and supported actions through proposals and approvalSlack
Grounded project contextReuse verified facts and inspect their sourcesMemory & Grounding
Test management and portabilityOrganize cases/scripts, import assets, and exchange QTMLTest management · QTML
Performancek6 workflows and migration guides for existing performance assetsPerformance
MobileResponsive readiness audits and managed mobile-flow guidanceMobile
EvidenceInterpret execution artifacts, signed verdicts, and exposure receiptsEvidence & Trust

Understand the PR gates

GatePurposeBehavior
AlphaReview the diff and run static security checksBlocking verdicts can fail the check
GammaRun a detected, supported native test suiteFailures can fail the check; skips when there is no applicable suite
DeltaRun QualityMax-generated project scriptsAdvisory warnings
BetaRun browser tests against a deployed previewTriggered by the successful deployment event; failures can fail the check

Configure your repository's required checks for merge enforcement. Enabled gates, supported frameworks, preview deployment events, and project settings determine what runs. The GitHub App and the explicit GitHub Action have different setup and execution paths. See gate verdicts for the decision rules.

Nexus on-demand specialist review is a separate workflow from automatic PR review. A Slack reply from one active specialist does not imply that a full multi-persona review ran.

Local tools and integrations

┌─ FIND YOUR WORKSPACE ────────────────────────────────────┐
│                                                          │
│   QualityMax                                             │
│   ├── In the browser                                     │
│   │   └── Hosted projects, tests, runs, and reports      │
│   ├── In your terminal                                   │
│   │   ├── qmax-code       Coding and QA agent            │
│   │   └── qmax            Platform CLI / local agent     │
│   ├── In your coding agent                               │
│   │   ├── qmax-mcp        Local browser QA tools         │
│   │   └── Free QA Skills  Reusable QA workflows          │
│   └── In your workflow                                   │
│       ├── GitHub          PR checks and Actions          │
│       └── n8n / Slack     Integrations and context       │
│                                                          │
└──────────────────────────────────────────────────────────┘
ProjectUse it forLicense / status
qmax-mcpFour standalone MCP tools: scan, inspect, generate a Playwright reproduction, run a testMIT
qmax-codeA QA terminal agent with standalone and hosted-connected modesSource available, FSL-1.1-ALv2
Free QA SkillsQA workflows inside supported coding agentsApache-2.0
9livesLocal test repair, reruns, and reviewable diffsMIT; prototype
Test GraderStatic Playwright test-quality gradingApache-2.0
Supply Chain ScannerPython dependency supply-chain checksApache-2.0
qmax local agentPlatform CLI and local test executionApache-2.0
GitHub ActionExplicit CI workflows with results and report linksMIT
n8n integrationConnect project, test, and performance workflowsMIT
qmax-receiptShared signed exposure-receipt schemaMIT

Local MCP versus hosted MCP: starting the standalone qmax-mcp package exposes its local tools without a QualityMax account. To use hosted projects and execution, follow the hosted MCP quickstart or the package's documented proxy mode. They are distinct connection paths.

For qmax-code installation, use the maintained source README and latest release. Advanced terminal commands can be experimental; check the source README for current availability.

See concrete examples

These examples demonstrate their named workflows; they are not live production certifications or universal performance benchmarks. The example guide explains what to inspect.

Deployment and embedding

The hosted application is the standard evaluation path. Sovereign is a private preview with design partners; supported topology and operational responsibilities are agreed during evaluation. Deployment guide

For embedding workflows and evaluating branding requirements, see Partner / White-label.

Help and contributions

Use documentation for setup and product behavior, issues for public bugs and documentation feedback, and CONTRIBUTING.md for contributions. Report sensitive issues through SECURITY.md.

This repository's license is separate from the licenses of the individual tools linked above.