Skip to content
Skills Library
Programming · Testing

testing-guidelines

/testing-guidelines

Language-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.

Licence
MPL-2.0
Last repository change
05.09.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
7
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

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

Licence

MPL-2.0, otwarta.

What it does and when to use it

Language-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.

Original author description

Language-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.

How it works

  1. Test Admission
  2. Existing-Test Review
  3. Effective Strategies for Test Admission and Review
Original SKILL.md headings · 55 lines, 392 words
SKILL.md preview
---
name: testing-guidelines
description: Language-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.
license: MPL-2.0
metadata:
  author: 'Basti Ortiz <ortiz@bastidood.dev>'
  source: 'https://github.com/BastiDood/skills'
---

# Testing Guidelines

This skill treats tests as protection for project-owned behavior, not as a coverage ritual. It favors cheap sans-I/O tests and rejects tests that merely restate test-double configuration, third-party libraries, or transparent wiring.

A meaningful test protects an exact project-owned invariant with an independently derived oracle at a level capable of observing a realistic defect. When the available infrastructure cannot provide that evidence, add no test and record the coverage gap when protection is still required.

## Test Admission

Test behavior that the project owns. Assume third-party libraries are correct and already tested.

Add a test only when it can fail because project-owned behavior is wrong.

Before adding or retaining a test, require all of the following:

- Name the exact project-owned invariant that the test protects.
- Name a realistic defect that violates that invariant and causes the test to fail.
- Derive the expected result independently of test-double configuration.
- Select the test level capable of observing that defect.
- Treat missing contract or integration infrastructure as a coverage gap. Test doubles cannot substitute for that infrastructure.

Project-owned behavior includes:

- Business rules and calculations.
- State-machine transitions and exhaustive decisions.
- Transformations that add domain meaning.
- Selection, retry, fallback, caching, and persistence policy.
- Error translation that adds a stable project contract.

Do not add a test when the implementation only forwards values to a dependency and returns its result unchanged.

## Existing-Test Review

Delete a test when it only:

- Repeats third-party documentation.
- Asserts schema-library mechanics.
- Verifies a one-to-one forwarding wrapper.
- Asserts test-double configuration.
- Checks getters, constructors, or field assignment without behavior.
- Exercises framework plumbing without a project-owned contract.

Do not preserve a useless test for coverage. Coverage is evidence of execution, not evidence of meaningful verification.

## Effective Strategies for Test Admission and Review

Follow the guidelines below. Read each linked reference that applies before writing, approving, or retaining tests.

1. Test only behavior that the project owns.
   - [Treat documented third-party dependencies as already verified.](./references/third-party-dependencies.md)
   - [Exclude tests that only prove delegation through transparent wrappers.](./references/transparent-wrappers.md)
2. Require independent evidence that a test protects a project-owned invariant.
   - [Reject circular fixtures and substituted-boundary claims with the test-double admission diagnostics.](./references/test-double-admission.md)
   - [Match each defect to an observable test level, including no test when the available level cannot provide meaningful evidence.](./references/test-level-selection.md)
Files in this package (7)
  • LICENSE.txt 16 KB
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • references/test-double-admission.md 3 KB
  • references/test-level-selection.md 2 KB
  • references/third-party-dependencies.md 1 KB
  • references/transparent-wrappers.md 1 KB

Versions

RepositoryScoreLicence
This page · Casper-Studios/casper-marketplace90MPL-2.0
getsentry/sentry-mcp100Apache-2.0
getsentry/warden100Apache-2.0
bastidood/skills90MPL-2.0

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

Downloads in the last 30 days: 0 · ranking

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

Similar skills

  • 95testing-principles
    This skill provides language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Automatically loaded when writing tests, designing test strategies, reviewing test quality, or when the user mentions "TDD", "test coverage", "unit…
  • 100testing-principles
    Language-agnostic testing principles for choosing which tests a change needs, test quality, and proof ownership, with frontend and browser E2E implementation references. Use when writing tests, deciding test scope, or reviewing test quality.
  • 100testing
    Stack-agnostic testing principles: test strategy, pyramid, test doubles, isolation, flaky tests, and antipatterns. Use to design a test strategy or review test quality.
  • 100testing
    TDD/BDD testing principles. Use when writing tests, reviewing test coverage, setting up testing, or discussing test strategy and test architecture.
  • 96coding-guidelines
    Coding and unit testing guidelines for C# and .NET, with review checklists and test naming examples. Use when writing, refactoring or reviewing C# code, unit tests or build scripts. Builds on the csharp-guidelines and http-api-guidelines skills.
  • 90typescript-testing
    Applies repository-aware TypeScript test design, behavior evidence, isolation, and mock-boundary criteria. Use when writing or reviewing unit tests.

Feedback and reports

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