Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Framework guide
Test-Driven Development source-backed Guide
Defines source-backed test-list, red-green-refactor, test design, isolation, refactoring, coverage, and delivery review, evidence handling, and action boundaries.
Read the fileOverview
Test-Driven Development Overview
source-backed framework bundle for test-list, red-green-refactor, test design, isolation, refactoring, coverage, and delivery review, evidence reconciliation, reviewable decisions, and controlled consequential.
Read the fileWorkflow
Test-Driven Development source-backed Triage
1. State the decision and direct answer possible now. 2. Record Verified, Provided, Assumed, and Needs verification separately. 3.
Read the fileTemplate
Test-Driven Development review brief
Review-ready artifact for test-list, red-green-refactor, test design, isolation, refactoring, coverage, and delivery review.
Read the fileIs this bundle right for your task?
Who it is for
- Practitioners using Test-Driven Development to structure analysis, decisions, facilitation, or review
- Teams working in Technology, Business operations
When to use it
- A team needs to apply Test-Driven Development to a concrete decision without skipping evidence, constraints, or stakeholder judgment.
- An existing analysis needs its assumptions, reasoning, affected parties, and review criteria checked.
What you need to provide
- The decision or question, available evidence, operating constraints, affected stakeholders, and desired outcome.
- Existing analysis, definitions, assumptions, examples, and review criteria that the framework must reconcile.
Tasks and expected outputs
Questions it helps answer
- Prepare a test-driven development review brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready decision with explicit verification and approval boundaries.
What it helps produce
- Test-Driven Development review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the decision or question, available evidence, operating constraints, affected stakeholders, and desired outcome. Ask the agent to apply Test-Driven Development and produce Test-Driven Development review brief that shows how evidence maps to the framework, where judgment is required, and what remains unresolved. Begin with martinfowler.com — Bliki / TestDrivenDevelopment, then confirm that the reference is current and applicable. Inspect Test-Driven Development source-backed Guide before drafting.
Context path: bundles/frameworks/test-driven-development
What the bundle includes
Frameworks
- Test-Driven Development
- source-evidence matrix
- qualified-review gate
Evaluations
- Test-Driven Development source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Applying the framework mechanically when the decision requires missing evidence, stakeholder judgment, or qualified review.
Known limitations
- Use the listed authoritative or identified source surfaces for general Test-Driven Development guidance; local facts, records, values, states, permissions, and results require inspected evidence.
- Task-specific work requires current evidence for requirement and behavior examples, test list, failing and passing test evidence, production code and diff, test doubles and boundaries, test command and environment, coverage meaning, refactoring evidence, CI results, owner, approvals, and rollback.
- Do not infer required behavior, test validity, failure cause, passing status, coverage adequacy, refactoring safety, or release readiness.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, student, and other sensitive data.
- Require explicit confirmation before actions that edit code or tests, run commands, install dependencies, commit or merge changes, change CI, deploy software, or claim defect prevention.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.