During smoke testing of a new software build, critical modules like login and payment fail while others pass. What is the most appropriate next action?

hard📝 Conceptual Q8 of 15

Testing Fundamentals - Testing Types and Levels

AProceed with detailed testing on the modules that passed

BReject the build and report the critical failures to the development team

CIgnore the failures and continue testing all features

DPerform sanity testing on the failed modules immediately

Step-by-Step Solution

Solution:

Step 1: Understand smoke test role
Smoke testing checks critical features to decide if build is testable.
Step 2: Analyze failure impact
Failures in critical modules mean build is unstable.
Step 3: Decide next step
Reject build and report issues; detailed testing should not proceed.
Final Answer:
Reject the build and report the critical failures to the development team -> Option B
Quick Check:
Critical failures stop further testing [OK]

Quick Trick: Critical failures mean build rejection [OK]

Common Mistakes:

Continuing testing despite critical failures
Confusing sanity testing with smoke testing next steps

Master "Testing Types and Levels" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Trace Try Challenge Automate Recall Frame

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Testing Fundamentals Quizzes

During smoke testing of a new software build, critical modules like login and payment fail while others pass. What is the most appropriate next action?

Step 1: Understand smoke test role

Step 2: Analyze failure impact

Step 3: Decide next step

Final Answer:

Quick Check:

Want More Practice?