Smoke testing and sanity testing in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is smoke testing?

Smoke testing is a quick set of tests to check if the basic functions of a software build work. It helps decide if the build is stable enough for detailed testing.

beginner

What is sanity testing?

Sanity testing checks specific parts of the software after changes or fixes to ensure those parts work correctly without testing everything.

intermediate

How is smoke testing different from sanity testing?

Smoke testing covers basic functions of the whole software to check stability, while sanity testing focuses on specific areas after changes to verify fixes.

beginner

When should smoke testing be done?

Smoke testing should be done right after receiving a new software build to quickly check if it is stable enough for further testing.

beginner

Why is sanity testing important?

Sanity testing saves time by checking only the changed parts of software after fixes, ensuring they work without running all tests again.

What is the main goal of smoke testing?

A Perform user acceptance testing

B Check if the build is stable for further testing

C Verify only fixed bugs

D Test all features in detail

Smoke testing quickly checks if the build is stable enough for more detailed testing.

Sanity testing is usually performed:

A Before receiving the build

B After major changes to the whole system

C Only during final release

D After small changes or bug fixes

Sanity testing focuses on verifying specific parts after small changes or bug fixes.

Which testing type covers basic functions of the entire software?

A Sanity testing

B Regression testing

C Smoke testing

D Performance testing

Smoke testing checks basic functions across the whole software.

If a build fails smoke testing, what should be done?

A Reject the build and fix issues first

B Proceed with detailed testing

C Perform sanity testing

D Ignore and release the build

Failing smoke testing means the build is unstable and should be fixed before further testing.

Sanity testing helps to:

A Save time by testing only changed parts

B Test the entire application thoroughly

C Check user interface design

D Measure software performance

Sanity testing focuses on changed parts to save time and effort.

Explain the difference between smoke testing and sanity testing.

Think about when and what each testing covers.

Why is smoke testing important in the software testing process?

Consider the role of smoke testing before deep testing.