Test strategy and coverage
Skill ldilov/harness-forge/skills/test-strategy-and-coverage
AI coding agent runtime that makes LLMs understand your codebase with repository-aware context, memory, and continuous learning
npx -y skills add ldilov/harness-forge --skill test-strategy-and-coverageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Define right-sized test layers and coverage priorities for a change.
SKILL.md
0.7 KB, 133 tokens by cl100k_base, as published. Nobody here has run it
Test Strategy And Coverage
Trigger Signals
- the task adds or changes behavior and the right test depth is unclear
Inspect First
- changed files, existing test layers, and validation commands
Workflow
- map the behavioral risk of the change
- choose the minimum test layers that cover that risk
- identify critical missing cases
- summarize the coverage strategy
Output Contract
- recommended test layers
- critical cases to cover
- explicit gaps or acceptable deferrals
Failure Modes
- no executable validation surface exists
Escalation
- escalate when a risky change has no trustworthy test path
Gives 0 of the 12 instructions most test skills give in 133 tokens
Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-06
- close the browser when donein 55 of 964, across 12 files
- wait for network idle statein 51 of 964, across 6 files
- launch chromium in headless modein 49 of 964, across 6 files
- use descriptive selectors for elementsin 49 of 964, across 6 files
- run provided scripts with help flag firstin 49 of 964, across 6 files
- add appropriate explicit waitsin 48 of 964, across 5 files
- use bundled scripts as black boxesin 46 of 964, across 3 files
- do not read script source codein 46 of 964, across 3 files
- use sync playwright for scriptsin 46 of 964, across 3 files
- inspect dom before executing actionsin 46 of 964, across 3 files
- run the full test suitein 36 of 964, across 34 files
- write the failing test firstin 25 of 964, across 18 files
Said here and by no other author read
- identify critical missing cases
- summarize the coverage strategy
- inspect changed files existing test layers and validation commands
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.