Bird
Raised Fist0

A developer writes unit tests but forgets to run them before committing code. How does this affect shift-left testing?

medium📝 Debug Q6 of Q15
Testing Fundamentals - Testing Models and Approaches
A developer writes unit tests but forgets to run them before committing code. How does this affect shift-left testing?
AIt breaks the shift-left process by delaying bug detection
BIt improves shift-left by adding more tests
CIt has no effect on shift-left testing
DIt speeds up testing by skipping unit tests
Step-by-Step Solution
Solution:
  1. Step 1: Identify the role of running unit tests early

    Running tests early is key to shift-left to catch bugs quickly.
  2. Step 2: Analyze impact of not running tests before commit

    Not running tests delays bug detection, breaking shift-left benefits.
  3. Final Answer:

    It breaks the shift-left process by delaying bug detection -> Option A
  4. Quick Check:

    Skipping early test runs = shift-left failure [OK]
Quick Trick: Run tests early to keep shift-left effective [OK]
Common Mistakes:
MISTAKES
  • Assuming adding tests without running helps
  • Thinking skipping tests speeds up process
  • Ignoring test execution importance

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Testing Fundamentals Quizzes