CtrlK
BlogDocsLog inGet started
Tessl Logo

testing-patterns

Cross-language testing strategies and patterns. Triggers on: test pyramid, unit test, integration test, e2e test, TDD, BDD, test coverage, mocking strategy, test doubles, test isolation.

Install with Tessl CLI

npx tessl i github:NeverSight/skills_feed --skill testing-patterns
What are skills?

72

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Evaluation results

93%

22%

Unit Tests for Order Pricing Engine

Unit test naming and AAA structure

Criteria
Without context
With context

Naming: unit segment

12%

100%

Naming: scenario segment

62%

87%

Naming: expected segment

50%

75%

AAA sections labeled

0%

80%

Arrange section present

85%

100%

Act section present

100%

100%

Assert section present

100%

100%

Correct test double type

60%

80%

Minimal mocking

100%

100%

Error cases covered

100%

100%

Avoids testing private/framework

100%

100%

All unit deps mocked

100%

100%

Without context: $0.3003 · 1m 6s · 16 turns · 23 in / 4,576 out tokens

With context: $0.5572 · 1m 51s · 29 turns · 279 in / 6,830 out tokens

86%

16%

Integration Tests for User Registration Service

Integration test DB isolation and service mocking

Criteria
Without context
With context

Real DB, not mocked

100%

100%

Transaction rollback isolation

0%

0%

External API mocked at boundary

60%

80%

Tests are independent

100%

100%

Integration scope

100%

100%

Happy path covered

100%

100%

Error/edge cases covered

100%

100%

Notification verified

100%

100%

Test naming convention

37%

100%

No unit-level mocking of internals

100%

100%

AAA pattern used

10%

100%

Without context: $0.6720 · 2m 30s · 36 turns · 41 in / 8,488 out tokens

With context: $0.6579 · 2m 8s · 35 turns · 38 in / 7,442 out tokens

97%

2%

Test Suite for a New Payment Processing Service

Test pyramid strategy and scope decisions

Criteria
Without context
With context

Pyramid proportions

100%

100%

Unit tests all-mocked

100%

100%

80% coverage target

100%

100%

E2E scope: critical flows only

100%

100%

E2E run timing

100%

100%

Business logic tested

100%

100%

Auth/permissions tested

100%

100%

Avoids framework internals

100%

100%

Avoids getter/setter tests

100%

100%

Test independence

100%

100%

Speed labels/targets

57%

57%

Naming convention followed

75%

100%

Error cases covered

100%

100%

Without context: $0.7725 · 3m 6s · 34 turns · 38 in / 12,171 out tokens

With context: $1.2533 · 4m · 33 turns · 471 in / 16,214 out tokens

Evaluated
Agent
Claude Code

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.