Test Writing Skill
Overview
Create thorough test coverage for software components.
Workflow
- •Analyze Code: Understand what needs testing
- •Identify Test Cases:
- •Happy path scenarios
- •Edge cases
- •Error conditions
- •Boundary values
- •Write Tests: Create test files following project conventions
- •Verify: Run tests to ensure they pass
- •Document: Add test descriptions
Test Types
Unit Tests
- •Test individual functions/methods
- •Mock dependencies
- •Fast execution
- •High coverage
Integration Tests
- •Test component interactions
- •Real dependencies when possible
- •Test data flow
- •API contracts
End-to-End Tests
- •Test complete user workflows
- •Real environment
- •Critical paths
- •User scenarios
Test Quality Standards
- •Clear test names describing what is tested
- •Arrange-Act-Assert pattern
- •One assertion per test (generally)
- •Independent tests (no shared state)
- •Fast and reliable
Tools
- •
view: To read code being tested - •
create_file: To create new test files - •
run_terminal_command: To execute test suites - •
grep_search: To find existing tests
Best Practices
- •Test behavior, not implementation
- •Cover edge cases thoroughly
- •Keep tests maintainable
- •Use descriptive test names
- •Don't test framework code
- •Mock external dependencies