it/

Package dbtest builds on pgenv: a migrated database and seeded users for the integration suites of the PostgreSQL stores.

Package evalenv is what the evaluator's integration tests need: the Web UI started for real inside the test process (see package stack), with a scripted agent behind it and a real PostgreSQL, and the way the evaluator starts Chrome.

Package leak fails a test that leaves behind goroutines of the application: a stream nobody reads, a run nobody cancelled, a pool nobody closed.

Package pgenv gives integration tests a real PostgreSQL through Testcontainers: one container per test binary, one fresh database per test.

Package stack runs the whole Web UI for integration tests, the way the program does: a real PostgreSQL (see pgenv), the scripted ADK agent behind a switch that can make it vanish, and the application served by the production server type, so that starting and shutting down are tested too.