Recipe catalog / requirement-testability
Check whether a requirement is testable
Decide whether a requirement defines an observable way to distinguish meeting it from failing it.
You need to check whether a requirement has clear, observable acceptance criteria before building it.
Explore this recipe interactively ยท Source and implementation guide
Use requirement-testability in TypeScript
Install with npm install jev-recipes. Requires Node.js 22.9 or newer and ES modules. Set TYPESAFE_API_KEY in your server environment for live calls, which send input to TypeSafe and use API quota. See the installation guide.
import { requirementTestability } from 'jev-recipes/requirement-testability';
const result = await requirementTestability({
"requirement": "The dashboard should load quickly."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| requirement | string | Required |
| context | string | Optional |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"requirement": {
"type": "string",
"description": "One requirement whose completion criteria need review."
},
"context": {
"type": "string",
"description": "Supplied definitions, acceptance criteria, and observation conditions."
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"requirement"
]
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"model": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"input_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"input_tokens",
"output_tokens"
],
"additionalProperties": false
},
"status": {
"type": "string",
"enum": [
"ready",
"review"
]
},
"verdict": {
"type": "string",
"enum": [
"testable",
"not_testable",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"testable",
"not_testable",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"testable",
"not_testable",
"unclear"
]
}
},
"required": [
"model",
"usage",
"status",
"verdict",
"confidence",
"probabilities"
],
"additionalProperties": false
}
}Saved example result
This hand-authored response demonstrates the contract. It is not a model accuracy measurement. Run it without an API key: npx jev-recipes demo requirement-testability.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "not_testable",
"confidence": 0.96,
"probabilities": {
"testable": 0.02,
"not_testable": 0.96,
"unclear": 0.02
}
}
Evaluation evidence
No verified live accuracy measurement is available. Evaluate representative cases before using this decision in your workflow.
Use the evaluation guide to measure this decision on your own labeled cases.
Limitations
- Assesses the wording and supplied definitions; does not generate tests, prove feasibility, or inspect an implementation.
- Exact measurements and pass/fail calculations belong in application code.
Related recipes
- step-complete: Use step-complete to check evidence against a condition that has already been defined.
- clarify: Use clarify to find missing information across a supplied list of requirements.