CtrlK
BlogDocsLog inGet started
Tessl Logo

platform-testing

Framework-agnostic testing principles — test philosophy, structure, mocking boundaries. Use when writing, reviewing, or debugging tests.

66

1.18x
Quality

51%

Does it follow best practices?

Impact

94%

1.18x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/platform/platform-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

83%

Fix Flaky Tests in Blog Platform

Test data factories

Criteria
Without context
With context

Dedicated factories file

100%

100%

UUID for entity IDs

100%

100%

nanoid for unique strings

0%

0%

nanoid import

0%

0%

Partial overrides parameter

100%

100%

Overrides spread last

100%

100%

Factory composition

100%

100%

No hardcoded shared IDs

100%

100%

Tests use factories

100%

100%

Override-only relevant fields

100%

100%

Multiple factories

100%

100%

99%

1%

Write Tests for Order Notification Service

Mock boundaries not internals

Criteria
Without context
With context

External API mocked

100%

100%

No internal module mocks

100%

100%

No database mocked

100%

100%

AAA structure

100%

100%

Behavior-named tests

100%

100%

One behavior per test

75%

87%

Independent tests

100%

100%

Integration over unit

100%

100%

Real state verified

100%

100%

100%

44%

Set Up Integration Test Infrastructure for a New TypeScript Microservice

Real database test infrastructure

Criteria
Without context
With context

docker-compose file created

100%

100%

postgres:16 image

0%

100%

Port 5433 mapped

100%

100%

fsync=off flag

0%

100%

full_page_writes=off flag

0%

100%

TEST_DATABASE_URL env var

0%

100%

Real DB connection in setup

100%

100%

No SQLite

100%

100%

No mocked DB

100%

100%

POSTGRES env vars set

100%

100%

Repository
ravnhq/ai-toolkit
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.