Testing

Testing Overview

JCC Express MVC ships with a Laravel-style testing layer that lets you test your application through real HTTP requests and database assertions — no mocking required.

How it works

Each feature test:

Boots a full Application instance (your real routes, middleware, providers)
Starts a temporary HTTP server on a random port
Makes real fetch() requests against it
Wraps the result in TestResponse so you can make fluent assertions
Tears the server down after each request automatically

Database state is isolated using withTransaction, which rolls back after every test body.

Two test runners — important

Runner	Command	Used for
`vitest`	`npm run test`	Unit tests (`tests/Unit/`)
`bun test`	`bun test tests/Feature`	Feature tests (`tests/Feature/`)

Feature tests import from bun:test and cannot run under Vitest. vitest.config.ts excludes tests/Feature/** for this reason. Always use bun test for feature tests.

Core classes

Class	Role
`TestCase`	Boots app, exposes HTTP + DB helpers
`MakesHttpRequests`	HTTP helper — `get`, `post`, `put`, `patch`, `delete`
`TestResponse`	Fluent response assertions
`InteractsWithDatabase`	DB assertions
`Factory` + `Faker`	Test data generation

Project test structure

TypeScript

tests/
  TestCase.ts          ← your project's base test case (extends framework TestCase)
  Feature/             ← HTTP / integration tests (bun test)
  Unit/                ← isolated logic tests (vitest)
Testing/
  Factory.ts           ← Factory + Faker helpers

Generate a test

Bash

bun artisanNode make:test UsersTest

Creates a starter file in tests/Feature/.