testing-standards
确保所有新屏幕/组件都有单元测试和适当的覆盖率。验证测试文件存在,包括加载、错误、成功和状态转换状态。检查后端处理程序是否有相应的测试文件。在创建或修改前端屏幕、组件或后端处理程序时使用。
📖 中文导读:确保所有新屏幕/组件都有单元测试和适当的覆盖率。验证测试文件存在,包括加载、错误、成功和状态转换状态。检查后端处理程序是否有相应的测试文件。在创建或修改前端屏幕、组件或后端处理程序时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: testing-standards description: Ensures all new screens/components have unit tests with proper coverage. Validates test files exist for loading, error, success, and state-transition states. Checks that backend handlers have corresponding test files. Use when creating or modifying frontend screens, components, or backend handlers.
Testing Standards
This skill enforces Ishkul's mandatory unit testing requirements to prevent production issues like the React error #310 caused by missing state transition tests.
Frontend Testing Requirements
Screens
Every new screen MUST have a test file at:
frontend/src/screens/__tests__/ScreenName.test.tsx
Required test coverage:
- Loading state - Initial loading UI
- Error state - Error handling and display
- Empty state - No data scenarios
- Success state - Data loaded correctly
- State transitions - Critical for catching React Rules of Hooks violations
Test File Template for Screens
describe('ScreenName', () => {
describe('Loading State', () => {
it('should display loading indicator', () => { /* test */ });
});
describe('Error State', () => {
it('should display error message', () => { /* test */ });
it('should allow retry', () => { /* test */ });
});
describe('Success State', () => {
it('should display data correctly', () => { /* test */ });
});
describe('State Transitions (Rules of Hooks)', () => {
it('should handle transition from loading to success', () => { /* test */ });
it('should handle transition from loading to error', () => { /* test */ });
it('should handle transition from error to loading (retry)', () => { /* test */ });
});
});
Components
Every new component MUST have a test file at:
frontend/src/components/__tests__/ComponentName.test.tsx
Required coverage:
- All props combinations
- User interactions (clicks, input changes)
- Edge cases (empty props, long text, etc.)
Backend Testing Requirements
Every new handler MUST have a test file at:
backend/internal/handlers/handler_name_test.go
Required coverage:
- Success cases
- Error cases (invalid input, auth failures)
- Edge cases
Running Tests
Frontend
# Run specific test file
npm test -- --testPathPattern="YourNewFile.test"
# Run all tests
npm test
Backend
go test ./...
Why This Matters
Missing state transition tests caused a production crash (React error #310) in LessonScreen where hooks were called after conditional returns. Always include state transition tests to catch these issues before deployment.