ComputeSphereLearn
Console
Learning paths / Vibe coding to production / Tests that prove something

Check: tests

Knowledge check · 5 min · Module 5, lesson 3 of 35 min left in this module

Module 5 · Tests that prove somethingLesson 3 of 3

Goal: Confirm you can write a test that fails first, and tell an agent's real tests from ones that can't fail.

Four questions: three on this module, one on Module 3. Every answer explains itself, right or wrong.

You write a test for a bug and run it before fixing anything. It fails with 'isOverdue is not a function'. What now?
Why do your isOverdue tests set now to a fixed moment, like 2026-10-01T15:30:00Z?
An agent adds a test named 'a task due today is overdue' that expects true. The suite is green. What's wrong?
From Module 3: before you let an agent edit, what should your brief ask it for?

Retry as often as you like.