testing-guidelines
/testing-guidelines
Określa niezależne od języka zasady dopuszczania testów dla zachowania należącego do projektu i sensownych dowodów sans-I/O przy dodawaniu, utrzymywaniu, usuwaniu i przeglądzie testów.
- Autor
- Casper-Studios ↗
- Repozytorium
- casper-marketplace ↗
- Licencja
- MPL-2.0
- Ostatnia zmiana repozytorium
- 05.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 05.09.2026, bez odwołań do wycofanych modeli i API.
MPL-2.0, otwarta.
Co robi i kiedy
Określa niezależne od języka zasady dopuszczania testów dla zachowania należącego do projektu i sensownych dowodów sans-I/O przy dodawaniu, utrzymywaniu, usuwaniu i przeglądzie testów.
Oryginalny opis (EN)
Language-agnostic test-admission rules for project-owned behavior and meaningful sans-I/O evidence. Use when adding, retaining, removing, or reviewing tests.
Jak działa
- Test Admission
- Existing-Test Review
- Effective Strategies for Test Admission and Review
Podgląd SKILL.md
--- 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)
Pliki w paczce (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
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Casper-Studios/casper-marketplace | 90 | MPL-2.0 |
| getsentry/sentry-mcp | 100 | Apache-2.0 |
| getsentry/warden | 100 | Apache-2.0 |
| bastidood/skills | 90 | MPL-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 1414f46332f0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95testing-principles
Podaje zasady testowania niezależne od języka: TDD, jakość testów, standardy pokrycia i wzorce projektowania testów. - 100testing-principles
Pomaga wybrać zakres testów dla zmiany i ocenić jakość testów, także testów E2E w przeglądarce. - 100testing
Opisuje niezależne od stosu zasady testowania: strategia testów, piramida, test doubles, izolacja, niestabilne testy i antywzorce, przy projektowaniu strategii lub przeglądzie jakości testów. - 100testing
Opisuje zasady TDD i BDD przy pisaniu testów, przeglądzie pokrycia i ustalaniu strategii oraz architektury testów. - 96coding-guidelines
Podaje zasady pisania testów jednostkowych i kodu w C# oraz .NET, wraz z listami kontrolnymi przeglądu i przykładami nazw testów. - 90typescript-testing
Stosuje kryteria projektowania testów TypeScript z uwzględnieniem repozytorium: dowody zachowania, izolację i granice mocków przy pisaniu lub przeglądzie testów jednostkowych.