Paths/Codex Engineer/Testing with Codex / Failing Tests
Read a Failure Before You Fix It
Half the generated fixes are wrong because nobody read the error. Write the routine that turns a red test into a correct change.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/codex/tests/reading-failures.md exists○
- The document states the order of reading a failure○
- The document states what to do when the failure is not the expected one○
02Walkthrough
1 of 4 revealed- 01
Create the tests directory
The routine lives with the other testing material.
mkdir -p ~/codex/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