Skip to main content

Testing

All Test Suites​

Run the Rust, Python, and JavaScript test suites together with:

just test

Test Database​

By default cargo test uses the dedicated test-postgres service from podman-compose.dev.yaml via TEST_DATABASE_URL=postgres://hypervibes:hypervibes@127.0.0.1:15433/postgres from .cargo/config.toml.

src/test_db.rs creates a fresh database for each pool() call when TEST_DATABASE_URL is set, runs migrations inside that database, and lets those isolated test databases be created concurrently on the dedicated test Postgres service.

The helper also does two cleanup passes:

  • a one-time startup sweep that drops stale vt_test_* databases left behind by earlier interrupted runs
  • per-test cleanup that closes the pool and drops the created database when the test handle is dropped

The dedicated test Postgres service is intentionally speed-optimized and disposable:

  • port 15433
  • max_connections=400
  • fsync=off
  • synchronous_commit=off
  • full_page_writes=off
  • shm_size=512m
  • tmpfs-backed PGDATA so test data never persists across container restarts

Frontend Build During Tests​

build.rs skips the automatic frontend pnpm build path during cargo test. Template and route tests render directly from source templates and do not need compiled assets. If you explicitly need the build-script asset step during a test invocation, run with HYPERVIBES_FORCE_FRONTEND_BUILD=1 cargo test.

SSE Tests​

The SSE route tests in src/web/routes.rs run in the normal suite against the dedicated test-postgres service. The shared read_sse_chunk helper still only reads an initial slice of each long-lived stream, so keep those tests focused on the initial event payload and explicit follow-up updates triggered inside the test.