Loading
Pick a focused question that fits your time, stack, and interview goal.
15 results across 1 active filter
Page 1 of 1
Explains pytest fixture dependency resolution, caching, lifetime, and the isolation cost of wider scopes.
Explains reverse-order fixture cleanup and designs teardown that remains safe when setup or tests fail.
Verifies commit callbacks without confusing callback registration with durable external delivery.
Overrides FastAPI boundaries for focused tests and restores the global override mapping reliably.
Uses parametrization for one behavior across meaningful cases while keeping failures and intent easy to read.
Aligns pytest-asyncio discovery, loop lifetime, and async fixture ownership without custom loop competition.
Separates fast rollback isolation from tests that must observe commits, multiple connections, or database concurrency.
Tests asynchronous coordination through observable events and proves spawned tasks finish or cancel cleanly.
Uses constrained Python mocks to catch interface drift and model asynchronous calls honestly.
Chooses Django database test isolation according to whether real commit and rollback behavior must be observed.
Uses generated examples to test stable invariants while preserving readable examples and reproducible failures.
Uses fixture factories and test-data builders to keep setup flexible, readable, and owned by each test.
Distinguishes unavailable conditions, known defects, and unstable tests while keeping lost coverage visible.
Chooses synchronous or asynchronous FastAPI test clients from the boundary exercised and resources involved.
Explains Python name binding and patches the reference actually used by the system under test.