When should I use testing-standards?

testing-standards is useful in the following scenarios: • Automating the validation of unit test coverage for new React screens to ensure loading, error, and success states are handled. • Enforcing mandatory test file creation for backend Go handlers to verify success paths and edge-case error handling. • Preventing production crashes (like React error #310) by requiring state transition tests for complex UI components. • Standardizing test file structures across a development team to maintain consistent code quality and documentation. • Verifying that all new UI components handle user interactions and various prop combinations before deployment.

testing-standards

from mesbahtanvir

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.

⭐1stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

The Testing Standards skill automates the enforcement of rigorous unit testing protocols for both frontend and backend development. It ensures that every new screen, component, and backend handler is accompanied by comprehensive test suites covering critical states—such as loading, error, and state transitions—effectively preventing production regressions and React 'Rules of Hooks' violations.

Use Cases

Automating the validation of unit test coverage for new React screens to ensure loading, error, and success states are handled.
Enforcing mandatory test file creation for backend Go handlers to verify success paths and edge-case error handling.
Preventing production crashes (like React error #310) by requiring state transition tests for complex UI components.
Standardizing test file structures across a development team to maintain consistent code quality and documentation.
Verifying that all new UI components handle user interactions and various prop combinations before deployment.

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.

name

testing-standards

description

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.