A software team wants to improve testing efficiency after frequent small updates. Which approach best combines smoke and sanity testing?

hard🚀 Application Q15 of Q15

Testing Fundamentals - Testing Types and Levels

APerform performance testing before smoke or sanity testing

BSkip smoke testing and run full regression after each update

COnly run sanity testing on all features after every update

DRun smoke testing on main features after every build, then sanity testing on specific fixes

Step-by-Step Solution

Solution:

Step 1: Understand testing goals for frequent small updates
To improve efficiency, quick checks are needed to catch major issues early, then focused checks on fixes.
Step 2: Evaluate combined approach of smoke and sanity testing
Running smoke testing on main features ensures build stability, followed by sanity testing on specific fixes ensures correctness of changes.
Step 3: Eliminate other options
Skipping smoke testing or running full regression every time is inefficient. Performance testing is unrelated to this goal.
Final Answer:
Run smoke testing on main features after every build, then sanity testing on specific fixes -> Option D
Quick Check:
Smoke then sanity for efficient small update testing [OK]

Quick Trick: Smoke test main features, then sanity test fixes for efficiency [OK]

Common Mistakes:

MISTAKES

Master "Testing Types and Levels" in Testing Fundamentals

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Testing Fundamentals Quizzes