Skip to main content
skill CX Codex

context-driven-testing — Claude Code skill: setup and guide

context-driven-testing adapts software testing strategies to specific project constraints, risks, and goals instead of blindly applying generic best practices.

MIT 125 installs ★ 533 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add proffesor-for-testing/agentic-qe --skill context-driven-testing -a claude-code
Open on GitHub

What context-driven-testing does

This skill instructs coding agents to inspect project reality before choosing test strategies. It applies Rapid Software Testing (RST) concepts like the SFDIPOT heuristic (Structure, Function, Data, Interfaces, Platform, Operations, Time), consistency oracles, and exploratory testing tours. The agent shifts from running passive checks to actively investigating product risks.

For coordinated fleets, the skill defines a memory structure under aqe/context-driven/ and selects specialized agents. An early-stage project receives minimal smoke tests on critical flows, while an enterprise system triggers deep regression tracking. Non-essential tools like visual testers are excluded early when budget or time is tight.

The skill contains no automated test runners or executable libraries; it functions strictly as reasoning instructions and agent coordination prompts.

What it helps with

  • Tailor test depth to product stage and compliance demands
  • Structure exploratory testing sessions using SFDIPOT heuristics
  • Filter sub-agents to prioritize critical risks over non-essential checks
  • Record testing rationale and discoveries in project memory

Example prompts for the agent

  • Analyze testing priorities for an early-stage SaaS with tight deadlines
  • Run an exploratory session on the checkout flow using SFDIPOT tours
  • Select relevant testing agents and rationale for a GDPR-regulated service

How to install context-driven-testing

1Skills CLI (Vercel)

npx skills add proffesor-for-testing/agentic-qe --skill context-driven-testing -a claude-code

2Manually: put the files in place

~/.claude/skills/context-driven-testing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/context-driven-testing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about context-driven-testing

How to install context-driven-testing in Claude Code?

Run npx skills add proffesor-for-testing/agentic-qe --skill context-driven-testing -a claude-code. Alternatively, place the file at ~/.claude/skills/context-driven-testing/SKILL.md.

What does context-driven-testing do?

It guides your agent to pick testing practices based on project risks, timeline, and goals rather than universal templates.

Does this skill include automated test suites?

No. It provides reasoning guidelines and agent selection rules; your coding agent writes the actual test scripts on demand.

Source text

SKILL.md · MIT
---
name: context-driven-testing
description: "Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs."
category: testing-methodologies
priority: high
tokenEstimate: 1100
agents: [qe-fleet-commander, qe-regression-risk-analyzer, qe-requirements-validator, qe-quality-analyzer]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [context-driven, rst, exploratory, heuristics, oracles, skilled-testing]
trust_tier: 0
validation:
---

# Context-Driven Testing

<default_to_action>
When making testing decisions or adapting approaches:
1. ANALYZE context: project goals, constraints, risks, team skills
2. QUESTION practices: "Why this? What risk does it address? What's the cost?"
3. INVESTIGATE not just check: Does software solve the problem, or create new ones?
4. ADAPT approach based on context, not "best practices"
5. DOCUMENT discoveries, not pre-written plans

**Quick Context Analysis:**
- Mission: "Find important problems fast enough to matter" (not "execute test cases")
- Risk: Safety-critical = high rigor; internal tool = lighter touch
- Constraints: Startup with tight timeline ≠ enterprise with compliance
- Skills: Novice needs structure; expert adapts intuitively

**Critical Success Factors:**
- No "best practices" work everywhere - only good practices in context
- Testing is investigation, not script execution
- Context changes; your approach should too
</default_to_action>

## Quick Reference Card

### When to Use
- Making testing decisions for new project
- Questioning "that's how it's done" dogma
- Adapting approach to specific constraints
- Exploratory testing sessions

### RST Heuristics
| Heuristic | Application |
|-----------|-------------|
| **SFDIPOT** | Structure, Function, Data, Interfaces, Platform, Operations, Time |
| **Oracles** | Consistency with history, similar products, expectations, docs |
| **Tours** | Business District, Historical, Bad Neighborhood, Tourist, Museum |

---

## Context-Driven Decisions

### Example: Test Automation Level

**Startup Context:**
- Small team, rapid changes, unclear product-market fit
- **Decision:** Light automation on critical paths, heavy exploratory
- **Rationale:** Requirements change too fast for extensive automation

**Enterprise Context:**
- Stable features, regulatory requirements, large team
- **Decision:** Comprehensive automated regression suite
- **Rationale:** Stability allows automation investment to pay off

### Example: Documentation

**Regulated (FDA/medical):**
- **Decision:** Detailed test protocols, traceability matrices
- **Rationale:** Regulatory compliance isn't optional

**Fast-paced startup:**
- **Decision:** Lightweight session notes, risk logs
- **Rationale:** Bureaucracy slows more than it helps

---

## Agent-Assisted Context-Driven Testing

```typescript
// Agent analyzes context and recommends approach
const context = await Task("Analyze Context", {
  project: 'e-commerce-platform',
  stage: 'startup',
  constraints: ['timeline: tight', 'budget: limited'],
  risks: ['payment-security', 'high-volume']
}, "qe-fleet-commander");

// Context-aware agent selection
// - qe-security-scanner (critical risk)
// - qe-performance-tester (high volume)
// - Skip: qe-visual-tester (low priority in startup context)

// Adaptive testing strategy
await Task("Generate Tests", {
  context: 'startup',
  focus: 'critical-paths-only',
  depth: 'smoke-tests',
  automation: 'minimal'
}, "qe-test-generator");
```

---

## Agent Coordination Hints

### Memory Namespace
```
aqe/context-driven/
├── context-analysis/*    - Project context snapshots
├── decisions/*           - Testing decisions with rationale
├── discoveries/*         - What was learned during testing
└── adaptations/*         - How approach changed over time
```

### Fleet Coordination
```typescript
const contextFleet = await FleetManager.coordinate({
  strategy: 'context-driven',
  context: {
    type: 'greenfield-saas',
    stage: 'growth',
    compliance: 'gdpr-only'
  },
  agents: ['qe-test-generator', 'qe-security-scanner', 'qe-performance-tester'],
  exclude: ['qe-visual-tester', 'qe-requirements-validator']  // Not priority
});
```

---

## Practical Tips

1. **Start with risk assessment** - List features, ask: How likely to fail? How bad? How hard to test?
2. **Time-box exploration** - 2 hours checkout, 30 min error handling, 15 min per browser
3. **Document discoveries** - Not "Enter invalid email, verify error" but "Payment API returns 500 instead of 400, no user-visible error. Bug filed."
4. **Talk to humans** - Developers, users, support, product
5. **Pair with others** - Different perspectives = different bugs

---

## Related Skills
- [agentic-quality-engineering](../agentic-quality-engineering/) - Context-aware agent selection
- [holistic-testing-pact](../holistic-testing-pact/) - Adapt holistic model to context
- [risk-based-testing](../risk-based-testing/) - Context affects risk assessment
- [exploratory-testing-advanced](../exploratory-testing-advanced/) - RST techniques

---

## Remember

**With Agents:** Agents analyze context, adapt strategies, and learn what works in your situation. Use agents to scale context-driven thinking while maintaining human judgment for critical decisions.

© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe

Similar skills

All skills for Testing and QA →

From the same set73

The whole set →
qe-coverage-analysis qe-coverage-analysis inspects Istanbul, c8, and lcov data to detect untested paths with risk scoring. Useful when prioritizing test efforts or checking PR quality gates. CX Codex +1 127installs test-reporting-analytics test-reporting-analytics generates quality dashboards, executive reports, and failure predictions based on code diffs. Useful when tracking CI/CD trends or preparing release gates. CX Codex +1 126installs qe-iterative-loop qe-iterative-loop — a skill that runs autonomous red-green-refactor cycles: the agent fixes failing tests, achieves coverage targets, and passes quality gates on its own. CX Codex +1 126installs xp-practices xp-practices — a skill for pair programming, continuous integration, TDD, and other extreme programming practices in AI coding. CX Codex +1 125installs n8n-integration-testing-patterns n8n-integration-testing-patterns is a Claude Code skill for testing API contracts, authentication flows, and rate limits in n8n integrations. CX Codex +1 124installs tdd-london-chicago tdd-london-chicago — a skill for choosing London or Chicago TDD, using mocks or real objects, and moving through the Red–Green–Refactor cycle. CX Codex +1 124installs qe-chaos-resilience qe-chaos-resilience — a skill for Claude Code, Codex, Cursor and other agents that injects controlled faults into distributed systems and checks recovery behavior. Runs during circuit breaker, failover, and retry logic validation. CX Codex +1 123installs consultancy-practices consultancy-practices is a Claude Code skill that applies software quality consulting practices: it identifies client pain, prioritizes work by impact and effort, and transfers knowledge. CX Codex +1 122installs

Project sponsors

Companies that keep this analytics open