nara-testing

Testing Patterns

Test layout

Keep tests near the Feature or subsystem they exercise:

src/features/<feature>/tests/   # Feature contracts, repositories, routes, clients
src/app/*.test.ts               # app composition and error handling
src/shared/**/*.test.ts         # shared modules
official-features/<feature>/tests/
tests/v3/                         # cross-cutting frontend, CLI, config, health

Use one focused test file per behavior or source module. Add a test when a changed contract or boundary would otherwise be uncovered; do not test incidental implementation details.

Running tests

During development, run the narrowest affected file:

npx vitest run src/features/auth/tests/routes.test.ts
npx vitest run tests/v3/frontend.test.ts
npx vitest run tests/v3/

Before delivery, run the repository check:

npm run check

The check covers the server typecheck (lint), the Vue typecheck (check:frontend), the Vitest suite, and nara doctor (architecture:doctor). Finish with npm run build when the change affects production serving.

Hono route tests

Exercise routes through the app's public HTTP boundary instead of calling private handlers:

import { randomUUID } from 'node:crypto';
import { describe, expect, it } from 'vitest';
import { app } from '../../../app/server';

describe('auth route', () => {
  it('rejects malformed input with field diagnostics', async () => {
    const response = await app.request('/api/auth/register', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({
        name: 'A',
        email: `${randomUUID()}@example.com`,
        password: 'short',
      }),
    });

    expect(response.status).toBe(422);
    await expect(response.json()).resolves.toMatchObject({
      success: false,
      code: 'VALIDATION_ERROR',
      errors: { name: expect.any(Array), email: expect.any(Array), password: expect.any(Array) },
    });
  });
});