Paths/Frontend Engineer/Testing Frontend Code / E2E & Mocks
Mock the Network, Not the Code
Mocking your own modules means every test asserts your implementation. Mocking at the network boundary keeps the test honest. Write the handler plan.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/tests/msw.md exists○
- The document states where the mocking happens○
- The document lists the handlers and the states they return○
02Walkthrough
1 of 4 revealed- 01
Create the tests directory
The mock plan is part 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