egipci-mcp: Instructions file for Kiro

Testing Guidelines

Testing Framework & Configuration

Vitest Setup

• Test Runner: Vitest with Node.js environment and global test functions
• Coverage Provider: V8 with 80% threshold for branches, functions, lines, and statements
• Test Files: *.test.ts or *.spec.ts in src/ directory, co-located with source files
• Setup File: src/test-setup.ts for global test configuration and mocks

Test Commands

pnpm test           # Run tests once
pnpm test:watch     # Watch mode for development
pnpm test:coverage  # Generate coverage report
pnpm test:ci        # CI mode with JUnit and coverage reports

Testing Patterns & Conventions

File Structure

• Place test files adjacent to source files: module-name.test.ts
• Use descriptive describe blocks for modules and functions
• Group related tests with nested describe blocks
• Use clear, behavior-focused test names with it('should...')

Import Patterns

import { describe, it, expect, vi, beforeEach, afterEach } from 'vitest'
import { functionToTest } from './module-name.js' // Use .js extension

Mocking Strategy

• External Dependencies: Mock HTTP clients (got), file system, and external APIs
• Global Mocks: Console methods and process.exit are pre-mocked in test-setup.ts
• Module Mocking: Use vi.mock() for external modules, preserve original exports when needed
• Function Mocking: Use vi.fn() for individual function mocks

Test Structure Template

describe('ModuleName', () => {
  beforeEach(() => {
    vi.clearAllMocks()
  })

  afterEach(() => {
    vi.restoreAllMocks()
  })

  describe('functionName', () => {
    it('should handle normal case', () => {
      // Arrange, Act, Assert pattern
    })

    it('should handle edge cases', () => {
      // Test boundary conditions
    })

    it('should handle error conditions', () => {
      // Test error scenarios
    })
  })
})

Specific Testing Requirements