Individual skill

testing-strategies

Good tests give you confidence to ship. Bad tests give you a false sense of security while slowing you down. The goal isn't 100% coverage - it's the right tests for the right things. This skill covers the testing pyramid (unit, integration, E2E), when to use each, mocking strategies, and the patterns that make tests maintainable. The key insight: test behavior, not implementation. Your tests should survive refactoring. 2025 reality: Jest is still king for JavaScript. Vitest is faster. Playwright dominates E2E. pytest owns Python. The real challenge isn't which tool to use - it's knowing what to test and how. Use when "test, testing, unit test, integration test, e2e, jest, vitest, playwright, cypress, pytest, mock, fixture, tdd, testing, jest, vitest, playwright, pytest, tdd, unit-testing, e2e" mentioned.

skills/testing-strategies/SKILL.md

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD

Yes

Scanner rules are current

No

Repository scan complete

No

Skill scan complete

No

Observed behavior

Not checked yet

Last checked

Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.