Scribd
Upload
10 views

Smoke Testing

Uploaded by

muralibgw
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
10 views

Smoke Testing

Uploaded by

muralibgw
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Smoke Testing:

Smoke testing, also known as "Build Verification Testing," is a preliminary


testing process designed to ensure that the basic functionality of a
software application is working properly. It is performed early in the
development cycle or after a new build/release is prepared. The goal is to
catch major issues early and prevent wasting time on more
comprehensive testing if the basic functionality is broken.

Examples of smoke testing scenarios:


1. Web Application:
 Verify that the homepage loads without errors.
 Check if user registration and login processes are functional.
 Test navigation to a few critical pages, like a product listing page or
a contact page.
 Ensure that the search functionality is working.
2. Mobile App:
 Check if the app launches without crashing.
 Test basic interactions such as tapping buttons and scrolling.
 Verify that essential screens like the main menu or settings page
are accessible.
3. Software Application:
 Ensure that the software installation process completes
successfully.
 Test basic operations such as opening, saving, and closing a file.
 Verify that important buttons and menu options are responsive.

Sanity Testing:

Sanity testing, also known as "Subset Testing" or "Quick Testing," is a


surface-level testing process that checks whether specific functionality or
areas of a software application have been fixed after a defect or issue has
been resolved. It is a cursory check to ensure that the major problems
have been addressed without going into detailed testing.

Examples of sanity testing scenarios:

1. Bug Fix Verification:


 After a critical bug has been fixed, perform a sanity test to verify
that the specific functionality related to the bug is working as
expected.
2. Regression Testing Subset:
 In a large application, after implementing new features, run a sanity
test on the core functionalities that are most likely to be affected by
the changes.
3. Integration:
 When integrating multiple systems, perform a sanity test to ensure
that the communication between systems is functioning after the
integration.
4. Compatibility:
 After making changes to support different browsers or devices,
perform a sanity test to verify that the application works as
intended on the targeted platforms.

You might also like