A test suite can be cheap to run and expensive to keep trustworthy. Repair minutes, flaky reruns, unclear ownership, and repeated setup work are maintenance costs that a pass rate hides.
Why this Skill is needed
The Test Maintenance Cost Analysis Skill examines change frequency, repair effort, flaky cost, ownership, maintainability, and confidence using supplied evidence. It turns cost signals into improvement options without inventing causal metrics.
What the Skill does
The goal is to expose the cost of trust, not to punish a test owner.
Use this Skill to review a suite, test area, or automation investment when maintenance burden is affecting feedback or trust. It does not decide staffing, release risk, or individual performance.
A good analysis names the cost signal, source, cohort, time window, confidence limit, priority, owner, close condition, and validation method.
Use it when flaky repair work is growing, tests break after UI or API changes, or no one can explain the cost of keeping a suite healthy.
What it does not do
The Test Maintenance Cost Analysis Skill can organize material, evidence, and next actions for Cost finding. 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 |
|---|---|---|
| Cost finding | What maintenance signal moved and for whom | Source and cohort |
| Confidence impact | How repair or flakiness affects trust | Evidence and limit |
| Improvement option | Refactor, isolate, retire, or instrument | Trade-off and owner |
| Validation | How to see whether cost or confidence changed | Window and method |
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 Cost finding, 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 Cost finding, 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 |
|---|---|---|
| Cost signals | Change frequency, repair effort, reruns, quarantine, ownership, and helper churn | Define event and window |
| Quality context | Risk protected, defect evidence, duration, and confidence impact | Do not optimize cost alone |
| Cohort | Suite, component, team, platform, and comparison period | Avoid moving cohorts |
| Decision boundary | Refactor, retire, isolate, or fund work | Human chooses the trade-off |
Use a request like this:
Use the test-maintenance-cost-analysis Skill.
Task: Analyze maintenance burden in the checkout UI suite after a design-system migration.
Inputs: [change history, repair tickets, reruns, quarantine list, ownership, runtime data, escaped defects]
Scope: [checkout UI tests for the last three releases]
Constraints: [do not infer team performance or release approval]
Cover change frequency, repair effort, flaky cost, ownership, maintainability, confidence, evidence state, and validation actions.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: Explain UI repair cost after a design-system migration
The suite’s selector repairs doubled, but most failures are in one shared helper and escaped defects did not increase. The Skill should separate helper maintainability from product-risk evidence, propose a focused helper refactor, and avoid saying the whole suite is ineffective or the team is unproductive.
The analysis describes supplied cost and confidence signals. It cannot prove a root cause, future savings, or staff performance without controlled comparison evidence.
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 Cost finding 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 Cost finding |
| Finding | The condition or result for Cost finding 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 |
|---|---|---|
| Cost finding | What maintenance signal moved and for whom | Source and cohort |
| Confidence impact | How repair or flakiness affects trust | Evidence and limit |
| Improvement option | Refactor, isolate, retire, or instrument | Trade-off and owner |
| Validation | How to see whether cost or confidence changed | Window and method |
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 event definitions, time window, suite and ownership cohort, repair records, reruns, quarantine, defect and risk context, and the decision to support. Keep missing cost fields unassessed.
A useful handoff includes input versions, scope, time window, evidence index, assumptions, Human decision boundary, and the smallest validation action.
Working with other Skills
- Test Suite Health Analysis:adds broader duration, flakiness, and duplication evidence.
- Test Runtime Optimization:handles runtime cost and execution baselines.
- Test Code Review:finds code-level maintainability risks.
Common traps
- Counting changed test lines as maintenance cost without repair context.
- Treating flaky reruns as tester productivity or quality failure.
- Retiring high-risk tests because they are expensive without recording residual risk.
Install and invoke
npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-maintenance-cost-analysis -gUse the test-maintenance-cost-analysis 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
Can this Skill rank engineers by maintenance cost?
No. It analyzes system and suite signals, not individual performance.
Is a flaky test always a candidate for deletion?
No. First understand protected risk, failure cause, isolation, and the cost of losing its signal.
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 Test Maintenance Cost Analysis 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
- Test Maintenance Cost Analysis prompt:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-maintenance-cost-analysis/prompts/test-maintenance-cost-analysis.md
- Test Maintenance Cost Analysis Skill source:https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/test-maintenance-cost-analysis
- Test Maintenance Cost Analysis details:https://inaodeng.com/en/qaskills/test-maintenance-cost-analysis/
- Awesome QA Skills on GitHub:https://github.com/naodeng/awesome-qa-skills