Repository navigation
buzz-db: shared test infrastructure (scratch DB, community seeding) #20
Description
Every test module that needs Postgres repeats the same boilerplate: PgPool::connect, create_scratch_db, make_community, insert_user, cleanup. There is no shared test utility module. A #[cfg(test)] test-utils submodule with common helpers would reduce duplication and make writing new integration tests easier. Priority: Low — developer productivity improvement.
🤖 AI review update (2026-08-23)
Clarify who must consume the helpers. A plain cfg(test) module works only inside buzz-db; cross-crate and integration tests need tests/common, a dev-only support crate, or a feature-gated support module. Prefer sqlx::test where it fits, unique per-test databases/schemas, deterministic seed builders, and cleanup guards safe under parallel execution.
Activity
TheSentinel454 commentedon Aug 24, 2026
🤖 Follow-up from block#6660: add a dedicated PostgreSQL test lane once the shared test infrastructure in this issue exists.
The block#6660 proving slice adds a deliberately focused selector for its four new
buzz-dbpersistence tests. That closes the immediate concurrency/rollback/mention-atomicity coverage gap, but it should not become the long-term pattern. The dedicated lane should automatically include all tests classified as PostgreSQL-backed so new DB tests are picked up without editing an exact test-name selector.Suggested scope / acceptance criteria:
#[ignore]plus hand-maintained names).buzz-db, relay unit tests, and integration tests.schema/schema.sqlcontract; exercise both intentionally where parity matters.Concrete blockers exposed by block#6660 validation:
publicschema and races other ignored PostgreSQL tests.type "channel_type" already exists.Reference: block#6660
ci: run PostgreSQL tests in isolated lane (#6730)
ci: run PostgreSQL tests in isolated lane (block#6730)