triad-testing

Testing with TriadJS

TriadJS tests run in-process. The runner invokes endpoint.handler(ctx) directly with a synthetic HandlerContext. No HTTP, no adapter, no JSON serialization. This makes tests fast and deterministic, and it means behaviors must not depend on Fastify/Express middleware.

triad.config.ts

Project root config file. Loaded with jiti, so TypeScript works with no build step.

import { defineConfig } from '@triadjs/test-runner';

export default defineConfig({
  router: './src/app.ts',                // module default-exporting the Router
  test: {
    setup: './src/test-setup.ts',        // default-exports a services factory
    teardown: 'cleanup',                 // method name on the returned services object
    bail: false,
  },
  docs: {
    output: './generated/openapi.yaml',
    format: 'yaml',                      // or 'json'
  },
  gherkin: {
    output: './generated/features',
  },
});

Field	Purpose
router	Path to the Router module (default export), resolved relative to the config file
test.setup	Path to a module whose default export is a services factory
test.teardown	Name of a method to call on the services object after each scenario
test.bail	Stop on first failure
docs.output / docs.format	Where triad docs writes
gherkin.output	Where triad gherkin writes

Configs are discovered by walking upward from the cwd unless --config is passed.

test-setup.ts — per-scenario isolation

Every scenario gets a fresh services container. The test setup file default-exports a factory:

// src/test-setup.ts
import { createServices } from './services.js';
import { createDatabase } from './db/client.js';

interface TestServices extends ReturnType<typeof createServices> {
  cleanup(): Promise<void>;
}

export default function createTestServices(): TestServices {
  const db = createDatabase(':memory:'); // fresh in-memory DB per scenario
  const services = createServices({ db });
  return {
    ...services,
    async cleanup() {
      services.db.$raw.close();
    },
  };
}