CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-isolation-patterns

Pure reference catalog of test-isolation and fixture-lifecycle patterns - the four-phase test pattern (Meszaros), fixture scope (per-test / per-describe / shared / global), the Fresh-Fixture vs Shared-Fixture trade-off (Fowler), parallel-safety patterns, and cleanup discipline (afterEach / afterAll / tagged-cleanup), plus a pattern-selection guide and a worked leaking-state diagnosis. The database-isolation strategies (transaction-rollback / database-per-worker / template-database) and network / external-service stubbing live in references/. This is the architecture-tier reference, not a file-level fixture-coupling style rule. Use when designing fixture scope and isolation strategy, auditing fixture coupling or retry/wait policy, or moving a suite to parallel execution.

88

Quality

88%

Does it follow best practices?

Impact

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured reference catalog that assumes Claude's competence and splits deep content into real, one-level-deep reference files. The main drag on conciseness is repetition of a couple of load-bearing facts across sections.

Suggestions

Cite the Luo et al. 2014 async-wait (45%) statistic once and refer back to it rather than repeating the full citation in Patterns 4, the cross-cutting anti-patterns, and the References section.

De-duplicate the 'never share mutable fixtures across tests' rule - state it once in Pattern 2 and reference it from Pattern 3 and the worked example instead of restating it.

Add a brief explicit validation checkpoint between 'How to use' steps (e.g., 'confirm the chosen scope holds under mutation before moving to parallel patterns') to strengthen workflow_clarity.

DimensionReasoningScore

Conciseness

Dense and information-rich, citing Fowler/Meszaros rather than re-teaching concepts Claude already knows, but the Luo 2014 45% async-wait statistic is repeated three times and the 'never share mutable fixtures across tests' rule is stated twice, so it could be tightened.

4 / 5

Actionability

Concrete, specific guidance throughout - 'Begin a transaction at test start; do all the test's DB work inside it; rollback at test end', framework syntax like '@pytest.fixture(scope=...)', and a real before/after JS worked example - with only minor gaps in runnable per-pattern commands.

4 / 5

Workflow Clarity

The 'How to use' section gives a clear 7-step sequenced procedure with a step-7 cross-check before sign-off; validation checkpoints between steps are mostly implicit rather than explicit, keeping it below a 5.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled one-level-deep references to the real files references/database-store-isolation.md and references/network-service-isolation.md, with deep DB/network content appropriately split out rather than inlined.

5 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is comprehensive, specific, and clearly scopes a distinct niche with explicit 'Use when' trigger guidance. Its only gap is missing the common everyday phrasing ('flaky tests'/'test flake') users would naturally say when reaching for this skill.

DimensionReasoningScore

Specificity

Enumerates concrete catalog contents - 'four-phase test pattern (Meszaros)', 'fixture scope (per-test / per-describe / shared / global)', 'Fresh-Fixture vs Shared-Fixture trade-off', 'parallel-safety patterns', 'cleanup discipline (afterEach / afterAll / tagged-cleanup)', plus 'a worked leaking-state diagnosis' - giving comprehensive coverage of specific capabilities.

5 / 5

Completeness

Explicitly answers 'what' (the catalog's enumerated contents) and 'when' with concrete triggers: 'Use when designing fixture scope and isolation strategy, auditing fixture coupling or retry/wait policy, or moving a suite to parallel execution.'

5 / 5

Trigger Term Quality

Strong natural trigger phrases - 'designing fixture scope and isolation strategy', 'auditing fixture coupling or retry/wait policy', 'moving a suite to parallel execution' - with good synonym coverage, but missing common user phrasings like 'flaky tests' or 'test flake' that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Claims a clear niche ('test-isolation and fixture-lifecycle patterns') and explicitly distinguishes itself - 'This is the architecture-tier reference, not a file-level fixture-coupling style rule' - minimizing overlap with sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents