Testing Strategies
Testing Strategies
Write tests that catch bugs, not tests that waste time
This skill provides strategies for effective testing at all levels, from unit to end-to-end.
Core Principles
1. Tests Are Documentation
Good tests explain what the code should do. They're living documentation that can't go stale.
2. Test Behavior, Not Implementation
Tests should verify outcomes, not internal details. Implementation can change; behavior shouldn't.
3. Fast Feedback Loops
Most tests should run in seconds, not minutes. Save slow tests for CI.
The Testing Pyramid
More from frankxai/arcanea
arcanea-architect
Expert guidance for building the Arcanea creative agent ecosystem with attention to detail, design excellence, and systematic implementation.
34agent-implementer
Implementation guidance for creating individual agents in the Arcanea system with proper structure, capabilities, and integration.
33arcanea-coding-agent
Arcanea creative agent integration for opencode
29opus-extended-thinking
Leverage Claude Opus 4.5's extended thinking capabilities for deep reasoning, complex analysis, and multi-step synthesis. Use when problems require thorough deliberation before response.
9hooks automation
Automated coordination, formatting, and learning from Claude Code operations using intelligent hooks with MCP integration. Includes pre/post task hooks, session management, Git integration, memory coordination, and neural pattern training for enhanced development workflows.
8web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
8