Getting Started
QE Workflows
Set up the QE pipeline — plan tests with /story-qa and execute them with /qe-run.
What Is This?
The QE pipeline is a two-workflow system for test planning and execution. /story-qa plans tests across 5 layers during story readiness, and /qe-run executes tests across 6 layers after development is complete.
The test plan from /story-qa flows directly into /qe-run — no re-discovery needed. Results are published to Jira with auto-created bug tickets for regressions.
Prerequisites
- Claude Code CLI installed and authenticated
- A repository with the framework copied in
- Jira MCP integration (recommended) — for publishing results and creating bug tickets
Setup
Copy the framework into your repo
Copy the .claude folder into the root of your repository. This folder contains both generators and all templates.
# From the framework source
cp -r .claude /path/to/your-repo/.claudeOpen Claude Code in your repo
Navigate to your repository root and launch Claude Code. It will automatically detect the .claude/commands/ directory and make the generators available as slash commands.
cd /path/to/your-repo
claudeGenerate story workflows (for /story-qa)
The story generator creates /story-qa alongside the other story readiness workflows. This is the test planning workflow that runs during story readiness.
/generate-story-workflowsGenerate QE workflows (for /qe-run)
The QE generator creates /qe-run — the test execution workflow. It runs 3 phases: survey (detects test stack, frameworks, test repo location), generate (builds all prompts), and validate (verifies file integrity, slot residue, signal flow, and Jira integration).
/generate-qe-workflowsStart using workflows
Plan tests during story readiness, then execute after development:
# Plan tests during story readiness
/story-qa DO-3238
# Execute tests after development is complete
/qe-run DO-3238
# Or run a single test layer
/qe-run DO-3238 --layer e2e
# Or re-run after fixing failures
/qe-run DO-3238 --rerunNext steps