Drift Testing
Generates and runs OpenAPI-driven contract tests via SmartBear's Drift CLI — but `drift verify` hard-requires a PactFlow account login, undisclosed in the skill.
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 14, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · d39749c
extract_endpoints.py and check_coverage.py ran for real against a bundled fixture spec and caught 4 of 7 missing response-code tests (401/403/404) that a hand-written baseline skipped — but `drift verify` itself refused to run with exit code 3 until we logged into a PactFlow tenant, a requirement the SKILL.md never mentions.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 6/10
- Docs & honesty 3/5
What Drift Testing does
Official Pactflow/SmartBear skill that parses an OpenAPI spec, scaffolds Drift test cases (auth patterns, coverage-gap-aware stubs), and runs a verify-and-fix loop against a live or Prism-mocked server, with a bundled Python coverage checker and feedback-loop runner. The bundled scripts (extract_endpoints.py, check_coverage.py) work standalone with just pyyaml and genuinely outperformed a hand-written baseline. But `drift verify` itself refuses to run (exit code 3, 'no PactFlow URL configured') until you log into a PactFlow tenant — a real setup step the SKILL.md and references/auth.md never state as mandatory for plain local verification.
How to install Drift Testing
git clone https://github.com/pactflow/pactflow-agent-skills
cd pactflow-agent-skills
mkdir -p ~/.claude/skills
cp -r plugins/swagger-contract-testing/skills/drift-testing ~/.claude/skills/api-contract-testing
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Drift Testing
-
/api-contract-testingGenerates and runs OpenAPI-driven contract tests via SmartBear's Drift CLI — but `drift verify` hard-requires a PactFlow account login, undisclosed in the skill.
It also activates on plain-language prompts like these:
-
Generate contract tests from this OpenAPI spec -
Check if our API implementation drifted from the spec -
Build a test suite that catches OpenAPI spec violations
Frequently asked questions
- Is the Drift Testing skill free?
- Yes. The skill itself is free from pactflow/pactflow-agent-skills. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Drift Testing work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 14, 2026. Verdict: Works with setup. extract_endpoints.py and check_coverage.py ran for real against a bundled fixture spec and caught 4 of 7 missing response-code tests (401/403/404) that a hand-written baseline skipped — but `drift verify` itself refused to run with exit code 3 until we logged into a PactFlow tenant, a requirement the SKILL.md never mentions.
- What is the Drift Testing SkillProof Score?
- 7.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 6/10, docs & honesty 3/5.
- How do I install Drift Testing?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Drift Testing with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.