Skip to content
Skills Library
Programming · Testing

eng-testing

/eng-testing

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

Repository
skills ↗
Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

Original author description

Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.

How it works

  1. Decide whether to write one
  2. Where it lives
  3. What it asserts
  4. Make it deterministic
  5. Stories and end-to-end tests
  6. Run the smallest check
  7. Review checklist
Original SKILL.md headings · 49 lines, 590 words
SKILL.md preview
---
name: eng-testing
description: Decide whether a change needs a test, where it lives, what it asserts, and which check to run before calling it done. Use when adding, moving, or reviewing a unit, component, integration, story, or end-to-end test, or choosing the smallest check to run before a PR.
---

# Testing

Add a test when it would catch a regression a reviewer would miss. Types, lint, a rendered component, or a run of the app prove most changes without one.

Repo facts (from AGENTS.md): the test policy (when a test is required, allowed, or discouraged), the runner and file pattern per package, shared test helpers and in-memory fakes, the lint rules that enforce test hygiene, the story or visual-test limits, which CI stage runs which tests, and the check commands from one file up to the pre-PR suite. The repo's policy wins over this skill. Before writing a test, search the installed skills for one that covers testing in the framework or runtime the code uses, and follow its helpers and patterns alongside this one.

## Decide whether to write one

- Write a test where a branch's behavior is uncertain or a past bug could return. Before writing it, ask whether the code can be split until the branch is obvious, or flagged for manual review in the PR. Prefer either when the repo's policy discourages tests.
- Skip tests that restate the implementation, check that something exists, cover a state the type system already forbids, or mostly exercise mocks.
- For a bug fix with a cheap regression path, follow `eng-tdd`.

## Where it lives

- Beside the code it covers (`foo.ts` and `foo.test.ts`), unless the repo puts tests in one tree.
- In the package or module that owns the code. Tests left at the app level cover integration and runtime boundaries (wiring, startup manifests, routing), not another package's internals. When code moves, its tests move in the same change.
- A pure lookup or format module gets one table test of accepted and rejected inputs.

## What it asserts

- Arrange, Act, Assert; one behavior per test.
- Assert a specific value, status, error type, or schema contract. "Is defined" and "is not null" pass for the wrong value.
- Component tests assert behavior, contracts, and accessibility semantics (roles, names, states), never CSS classes, styling, or raw markup. Visual checks belong in rendered stories or screenshot tests.
- No focused or skipped tests (`.only`, `.skip`) in a commit.

## Make it deterministic

- Provide dependencies as in-memory fakes that behave like the real ones, not hand-built mocks of client calls.
- Control time and randomness through an injected clock and random source, not by stubbing globals.
- Test failure paths, retries, cancellation, and cleanup where their behavior is uncertain; do not test the framework's own behavior.

## Stories and end-to-end tests

- Keep component stories bounded: one gallery or matrix story for visual variants and at most one interaction story for state, keyboard, or focus. No story per minor variant.
- End-to-end tests cover critical user journeys only. Know which CI stage runs them and how to force a run.

## Run the smallest check

Run one file, then the changed packages, then the repo's pre-PR suite. Use the repo's task runner rather than a bare test binary when it builds dependencies or generated types first. Know which tests the PR's CI skips.

## Review checklist

- Each new test covers an uncertain branch or a past bug; otherwise it is deleted or the code is simplified.
- Tests sit beside the code, in the module that owns it, and move with it.
- Every assertion names a value or contract; none is vacuous, styling-based, focused, or skipped.
- Time, randomness, and services come from fakes and an injected clock.
- Story count stays bounded.

Versions

RepositoryScoreLicence
This page · jpoehnelt/skills90MIT
duronext/jig100MIT

Database snapshot: 13.11.2026 · package version 33d8a399b869 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 2 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90testing-strategy
    Use when the task involves deciding whether a change needs a new test, choosing how to validate a change in this repository, deciding whether to inspect a running dev server, run unit tests, run Playwright UI screenshot tests, or avoid unnecessary builds, or when a test fails…
  • 100testing
    Run the test tiers a code change in cap-evolve needs before review - the unit tier always, and a real end-to-end run (local zero-API or a dispatched CI benchmark/integration-test leg) when the change plausibly affects a real run. Use for every code change (core/cap_evolve,…
  • 100testing-strategy
    Use when planning or reviewing tests for a code change, choosing between unit, focused regression, integration, contract, end-to-end, performance, security, property-based, or agent-evaluation checks; classify change risk first and select the smallest evidence set that proves…
  • 100test-strategy
    Decides what to test and at which level, then writes fast, deterministic tests that check behavior rather than implementation details. Use when planning how a feature or system should be tested, choosing between unit, integration, contract and end-to-end tests, deciding what to…
  • 96measure
    Run the project's full test suite, time it, and record the run in eng-kit (local only). Use when the person asks to measure or benchmark the full suite.
  • 95tester
    Plans every kind of test, requires they are run, and judges whether the product meets the standard. Use when planning tests, deciding whether work is really done, or reviewing a project before release: unit, integration, end-to-end, accessibility, performance, environment and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.