Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
Senior Deep-Dives
›
Module 4 · Memory + profiling · Recap
›
Testing pyramid: unit > integration > e2e
quiz
92 / 161
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** Symptoms of an inverted pyramid? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** Symptoms of an inverted pyramid? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Coverage stuck around 60% — unit tests stay shallow because integration tests already exercise the same paths.
B
Flaky CI, hour-long suites, fear of merging. Inversion = relying on slow e2e for things unit tests should catch.
C
Lots of small mock objects — too many `MagicMock` instances drive every assertion down to internal call counts.
D
A test class per source file — mirroring the source tree fragments the suite and confuses pytest's collection step.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…