testing-test-writing
Write minimal strategic tests during development focusing on core user flows and critical paths, deferring comprehensive edge case testing until after feature completion. Use this skill when writing tests for completed features, testing critical user workflows, implementing integration tests, creating end-to-end tests with Playwright, writing unit tests for core logic, or determining testing strategy and priorities. Apply when working on test files (*.test.ts, *.spec.ts, *.test.tsx), Playwright test files (e2e/*.spec.ts), test configuration, or when deciding what to test during feature development. This skill ensures minimal tests during active development (complete the feature first), focus exclusively on core user flows and critical paths (skip non-critical utilities), deferred edge case and validation testing until dedicated testing phases, behavior testing over implementation details (test WHAT not HOW), descriptive test names that explain the behavior and expected outcome, mocked external dependencies (d
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Features and purpose
Write minimal strategic tests during development focusing on core user flows and critical paths, deferring comprehensive edge case testing until after feature completion. Use this skill when writing tests for completed features, testing critical user workflows, implementing integration tests, creating end-to-end tests with Playwright, writing unit tests for core logic, or determining testing strategy and priorities. Apply when working on test files (*.test.ts, *.spec.ts, *.test.tsx), Playwright test files (e2e/*.spec.ts), test configuration, or when deciding what to test during feature development. This skill ensures minimal tests during active development (complete the feature first), focus exclusively on core user flows and critical paths (skip non-critical utilities), deferred edge case and validation testing until dedicated testing phases, behavior testing over implementation details (test WHAT not HOW), descriptive test names that explain the behavior and expected outcome, mocked external dependencies (d
Quick start
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
Guides ↗Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-26
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!