create-test

You are $DEV_ROLE, writing unit tests for the $PROJECT_NAME project.

Why writing tests matters

The quality scorer measures test_discipline: the % of commits that touch test files.

• 25% of commits with tests = 100 points
• Test files are recognized by: /tests/, /test/, /__tests__/, /spec/, test_*, *_test.*, *.test.*, *_spec.*, *.spec.*

Goal: for every 3-4 code commits, have 1 test commit

Input

$ARGUMENTS — the file or module that needs tests. Example: src/modules/chat/hooks/use-chat-page.ts

If absent, check git diff dev...HEAD --name-only and write tests for the changed files.

Actions

Step 1: Read the file to test

Read the source file to understand the logic, dependencies, and edge cases.

Step 2: Create the test file

Place the test file in the corresponding location:

• Hook: src/modules/{module}/__tests__/{hook-name}.test.ts
• Utility: src/core/utils/__tests__/{util-name}.test.ts
• Component: src/modules/{module}/__tests__/{component-name}.test.tsx
• Store: src/app/stores/__tests__/{store-name}.test.ts
• API hook: src/core/api/__tests__/{api-hook-name}.test.ts

Step 3: Write the test from the template

import { renderHook, act } from '@testing-library/react-hooks'
// import source under test

describe('{ModuleName} - {FunctionName}', () => {
    beforeEach(() => {
        // reset mocks
        jest.clearAllMocks()
    })

    describe('happy path', () => {
        it('should {expected behavior} when {condition}', () => {
            // Arrange
            // Act
            // Assert
        })
    })

    describe('edge cases', () => {
        it('should handle empty input gracefully', () => {
            // test null/undefined/empty
        })

        it('should handle error state correctly', () => {
            // test error scenarios
        })
    })

    describe('boundary conditions', () => {
        it('should {boundary behavior}', () => {
            // test limits, max values, etc.
        })
    })
})