fixtures

Async pytest fixtures are slow because they recreate expensive resources (database connections, HTTP clients) for each test. Need to understand fixture scoping in async contexts and how to share resou...

Test fixtures are duplicated across multiple test files. Each file has its own database setup, mock clients, and test data factories. Need a way to share fixtures across an entire test suite without i...

Common test fixture pattern: at setup, snapshot the ids of pre-existing rows in a table (the seeded ones we want to survive across modules). At teardown, delete every row whose id is NOT in that snaps...

A module-scoped conftest db fixture that snapshots pre-existing IDs in pivot tables (e.g. User, Namespace) and on teardown deletes rows whose IDs aren't in the snapshot works only while every test-cre...

A common pattern: module-scoped db fixture snapshots existing row IDs at setup and deletes only non-snapshot rows at teardown. Two failure modes: (a) rows seeded by a now-removed init path persist ind...