AI Features
Claude Code Plugin
The Qualflare plugin for Claude Code brings test coverage into your AI
coding sessions. After a one-time /qf-init,
generate tests for changed files, run your suite and upload results, and fix failures — all without leaving the chat.
Product news and testing tips.
Why it matters
Coverage stalls mid-session
You know you should add a test for what you just changed. Switching context to write it later usually means it never happens.
AI-written code, untested by default
An AI coding session moves fast — fast enough that test coverage quietly falls behind unless something reminds you.
Fixing a failing suite means leaving the chat
Debugging a broken test usually means tabbing out to a terminal, running it, reading the output, and tabbing back.
How it works
Each command picks up where the last left off: /qf-cover proposes
and writes tests for what you just changed, /qf-run executes
the suite and uploads results, and /qf-fix patches
whatever failed — a typical session looks like this:
What you get
One-time setup: /qf-init
Detects your frameworks, writes a test-state file, configures auth and a session-end hook, and updates your CLAUDE.md — once.
Generate tests for changed files
/qf-cover proposes tests for whatever you just edited and writes them to disk once you approve.
Run and upload in one command
/qf-run runs your suite and uploads the results to Qualflare — the same collect pipeline the standalone CLI uses.
Fix failures without leaving the chat
/qf-fix analyzes what broke in the last run and patches the source until the suite is green again.
A session-end coverage nudge
At the end of a session, if you've made a substantive change to a source file with no matching test edit, the plugin leaves a one-line nudge instead of silently letting coverage drift:
Toggle this on or off anytime with /qf-hook off.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
What is the Qualflare plugin for Claude Code?
It brings test coverage into your AI coding sessions inside Claude Code. After a one-time /qf-init, you can generate tests for changed files, run your suite and upload results to Qualflare, and fix failures — without leaving the chat. It works with the same 23 frameworks the Qualflare CLI supports.
How is this different from the in-app Quo Agent?
They're different surfaces for different moments. The Claude Code plugin operates inside Claude Code, at the point you're writing code — it generates and fixes tests directly. Quo is a panel inside the Qualflare web app that analyzes coverage gaps, suggests test cases, and generates test steps — it doesn't write or fix source code.
What slash commands does it add?
/qf-init (setup), /qf-cover (generate tests for changed files), /qf-run (run + upload results), /qf-fix (fix failing tests from the last run), /qf-doctor (health check), /qf-update (refresh file counts), /qf-state (inspect current state), and /qf-hook (toggle the end-of-session coverage nudge).
Which frameworks does it support?
The same 23+ frameworks as the Qualflare CLI — Playwright, Cypress, Jest, pytest, JUnit, Go, RSpec, PHPUnit, TestNG, Cucumber, Karate, TestCafe, Maestro, XCTest, Espresso, Newman, k6, OWASP ZAP, Trivy, Snyk, SonarQube, and any other JUnit-XML-compatible output.
Do I need a Qualflare account to use it?
/qf-init walks you through authentication as part of one-time setup — the same account used by the Qualflare CLI and web app, since /qf-run uploads results through that account.