Paths/Backend Engineer/Testing Backend Code / The Test Layers
Make the Database Testable
Integration tests fail for boring reasons - a leftover row, a migration that did not run. Write the database strategy that removes them.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/tests/integration.md exists○
- The document states how the test database is provisioned○
- The document states how migrations and isolation are handled○
02Walkthrough
1 of 4 revealed- 01
Create the tests directory
The integration notes live with the rest of the test strategy.
mkdir -p ~/tests - 3 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list