Paths/Frontend Engineer/Testing Frontend Code / Component Tests
Test Behaviour, Not Implementation
The value of a test is what it protects. Write the rule that keeps the suite about behaviour.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/tests/behaviour.md exists○
- The document states what to assert on○
- The document states what not to couple the tests to○
02Walkthrough
1 of 4 revealed- 01
Create the tests directory
The rule is one page, and it saves an afternoon every time it is forgotten.
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