A timeout is not just a number. It changes whether downstream work continues, whether the user sees a recoverable state, and whether a retry risks repeating an operation.
Why this Skill is needed
The Timeout Testing Skill prepares evidence-bounded analysis of timeout budgets, cancellation propagation, downstream boundaries, user feedback, and retry interaction. It keeps a timeout design separate from a completed fault run.
What the Skill does
The important boundary is what still runs after the caller has stopped waiting.
Use this Skill when an API, job, UI flow, or dependency chain needs explicit timeout behavior and safe validation. It does not inject faults or access production systems.
A good review names each timeout budget, owner, cancellation path, downstream effect, user-visible result, retry rule, evidence source, stop condition, and validation method.
Use it when a service adds a dependency, users report hanging requests, or timeout and retry behavior is inconsistent across layers.
What it does not do
The Timeout Testing Skill can organize material, evidence, and next actions for Budget map. It does not replace:
- Confirmation of rules, scope, and risk by the accountable domain owner.
- A real environment, account, dataset, log, or run record; static analysis does not become runtime evidence by itself.
- Authorization for release, compliance, production actions, or residual-risk acceptance.
- A Human decision when supplied sources conflict.
What it checks
The value of this Skill is not another keyword list. It connects each focus area to an observable input, a judgment, and a way to close the loop. Start with a small matrix based on the source Skill’s output contract:
| Focus | Question before analysis | Handoff output |
|---|---|---|
| Budget map | Timeout at each layer and its relationship | Source and gap |
| Cancellation finding | What stops, continues, or persists | Evidence state |
| User and retry behavior | Visible state and duplicate-side-effect risk | Contract and evidence |
| Validation action | Smallest controlled delay or replay | Stop condition |
If a row has only a conventional expectation and no source or validation method, keep it open instead of turning it into a pass.
Audit inputs before you start
Before analyzing Budget map, classify the input into six evidence states. A gap is not automatically a failure, but it must not disappear inside the conclusion.
| State | Meaning | How this Skill should handle it |
|---|---|---|
| known | Directly supported by the supplied material | Keep the source, version, and time with the judgment |
| missing | Needed for this pass but not supplied | Name the smallest evidence action and limit the conclusion |
| conflicting | Sources disagree | Show both sources and route the conflict to an owner |
| stale | Present but outside the relevant version or time window | Mark freshness; old evidence is not current proof |
| out_of_scope | Related but excluded from this pass | Keep the boundary explicit |
| assumptions | Temporarily adopted to continue analysis | State how and when the assumption will be checked |
Keep the input version, scope, environment, evidence locations, and accountable owner together. Without a run record, deliver analysis, design, or a validation plan—not an execution pass.
From problem to structured Finding
Connect the source, scope, evidence state, analysis, owner, action, close condition, and validation before writing the conclusion. The case below keeps this Skill’s identifier and domain context.
Keep the decision layers separate
For Budget map, do not compress four different kinds of language into “recommended to pass”:
| Layer | How to write it | Application here |
|---|---|---|
| Fact | What the supplied material directly shows | Cite the source, version, input, or run record for the focus |
| Evidence-backed Inference | What several facts support together | Show the inference chain and retain uncertainty |
| Recommendation | The smallest next action | Name the evidence, review, execution, or regression path |
| Human Decision | What an accountable person must decide | Leave scope, risk acceptance, resources, and release meaning to the owner |
A complete case
This case follows Input, Analysis, Finding, Decision, and Validation. When material is incomplete, keep missing, conflicting, or assumptions visible instead of turning them into a pass.
Input
| Material | What to provide | What to do when it is missing |
|---|---|---|
| Timeout chain | Client, gateway, service, database, queue, and provider budgets | Keep missing budgets pending |
| Cancellation behavior | Signal propagation, cleanup, partial work, and persistence | Do not infer cancellation |
| User feedback | Error state, progress, retry affordance, and support signal | Separate expected from observed |
| Retry interaction | Idempotency, attempt limit, backoff, and side effects | Link to the operation contract |
Use a request like this:
Use the timeout-testing Skill.
Task: Review a report-download flow where the browser times out after 30 seconds but the export job continues and can be retried.
Inputs: [timeout budgets, cancellation behavior, job state model, retry policy, logs, user messages]
Scope: [staging export flow]
Constraints: [no production fault injection]
Cover budgets, cancellation propagation, downstream boundaries, user feedback, retry interaction, evidence state, and safe validation.Analysis
Use the input, matrix, and evidence state to form the judgment before writing the Finding; keep missing material as a gap.
Finding
Focused example: Stop waiting without losing track of the export job
The browser reports timeout at 30 seconds, but the job continues and a second click creates another export. The Skill should separate caller timeout from downstream cancellation, require a job-status or idempotency decision, and propose a staged delayed-provider validation. It should not assume the UI timeout cancelled server work.
The analysis prepares timeout validation and evidence classification. It cannot prove cancellation, user experience, or duplicate-side-effect safety without an authorized run.
Example finding: turn one problem into a handoff
The field example below shows the recording pattern; it is not an execution result.
If the supplied material cannot prove that Budget map meets its contract, write the finding like this. It does not invent the missing rule or turn missing evidence into a failure.
| Field | Example wording |
|---|---|
| Source and scope | Record the requirement, version, environment, and the concrete object for Budget map |
| Finding | The condition or result for Budget map is not yet traceable to evidence |
| Evidence state | missing / assumptions; use conflicting when sources disagree |
| Impact and priority | Name the affected user, journey, or delivery decision without inflating severity |
| Owner and Human decision | Ask the product, engineering, security, or test owner to confirm the rule and trade-off |
| Action and close condition | Add the smallest missing evidence; close only when source, judgment, and owner can be reviewed |
| Validation | Name one repeatable check, query, or run and retain the raw artifact |
The point is to let the next person walk from the finding back to the source and run an action that can change the decision.
Decision
The accountable owner confirms the decision question and risk trade-off; the Skill does not make that choice.
Validation
Before closing the finding, run the stated validation and retain the raw artifact. Without an execution record, the status remains unverified.
How a Finding enters the next stage
Handoff output
| Output field | Why it exists | Example status |
|---|---|---|
| Budget map | Timeout at each layer and its relationship | Source and gap |
| Cancellation finding | What stops, continues, or persists | Evidence state |
| User and retry behavior | Visible state and duplicate-side-effect risk | Contract and evidence |
| Validation action | Smallest controlled delay or replay | Stop condition |
Every conclusion should point to a source, evidence state, and next action. If evidence is missing, use pending, blocked, unassessed, or NOT_SCORED instead of filling the gap with confidence.
Next-stage route
At minimum, hand off the source, evidence state, owner, close condition, and validation action; the next-stage conclusion remains bounded by the evidence state.
How to prepare better input
Provide timeout budgets, layer ownership, cancellation and persistence rules, job state, retry/idempotency contract, user messages, environment, and safe delay mechanism. Missing budgets remain pending.
A useful handoff includes input versions, scope, time window, evidence index, assumptions, Human decision boundary, and the smallest validation action.
Working with other Skills
- Retry Testing:examines repeated attempts and side effects.
- API Error Contract Testing:checks timeout and error response contracts.
- Circuit Breaker Testing:checks repeated downstream failure boundaries.
Common traps
- Setting every timeout to the same value without accounting for downstream work.
- Assuming a client timeout cancels server or provider work.
- Retrying a timed-out write without checking idempotency and job status.
Install and invoke
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/timeout-testing -gUse the timeout-testing Skill.
Include objective, scope, versions, evidence paths, constraints, and decision boundary.
Audit inputs first, preserve evidence states, and finish with owner, close condition, and validation method.FAQ
Is a shorter timeout always better for users?
No. It may improve responsiveness while leaving work running or creating ambiguous completion; budgets and cancellation need evidence.
Should a timeout automatically retry?
No. Retry depends on operation safety, error classification, idempotency, and user-visible state.
The Skill is most useful when attached to one real project artifact and kept with its source evidence. Start narrow, validate the uncertain part, and expand only when evidence supports it.
References
Source Skill and execution contract
The complete execution contract lives in Timeout Testing prompt. The source directory may also contain evaluation cases and supporting material.
Static plans, file presence, and dry runs keep their evidence state. They do not become runtime proof, an all-passed claim, or release approval.
Reference links
- Timeout Testing prompt:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/timeout-testing/prompts/timeout-testing.md
- Timeout Testing Skill source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/timeout-testing
- Timeout Testing details:https://inaodeng.com/en/qaskills/timeout-testing/
- Awesome QA Skills on GitHub:https://github.com/naodeng/awesome-qa-skills