Smoke Testing & Sanity Testing

Smoke Testing

1. What is Smoke Testing:

Checks whether the basic and critical features of the application work properly.

2. When Smoke Testing is performed:

After receiving a new build from the developer
Before starting detailed testing
When a major build is released

3. Where Smoke Testing is used:

In the Testing phase
In Agile, Waterfall, and V-Model projects
In the QA / Testing environment
When a new build is released

4. How Smoke Testing Work:

Checks main functionalities only
Done quickly
Ensures the build is stable

Example checks:

Application opens
Login works
Main page loads
Basic navigation works

5. Example

Smoke Testing Example (E-Commerce Website):

Tester checks:
Website opens
User can login
Products are displayed
Add to cart works
Checkout page opens
Tester does NOT check:
UI alignment
Edge cases
Detailed payment validation

1. What Sanity Testing:

Checks whether a specific bug fix or small change works correctly.

2. When Sanity Testing is performed:

After a bug is fixed
After small code changes
After minor feature updates

3. Where Sanity Testing is used:

In the Testing phase
On a specific module or feature
In the QA / Testing environment
After small updates in the application

4. How Sanity Testing Work?

Checks only the changed or fixed functionality
Focuses on specific modules
Ensures the bug fix works properly

Example checks:

Login bug fixed → Test login again
Check if user successfully logs in
Verify dashboard opens

5. Example

Sanity Testing Example:

Bug:

User cannot login with correct username and password.
Developer fixes the bug.
Tester performs Sanity Testing:
Open application
Enter valid username & password
Click login
Check if user logs in successfully
Verify dashboard opens

If login works → Continue testing

If login fails → Bug is reopened.

Simple Final Line

Smoke Testing: Checks if the whole application is stable.

Sanity Testing: Checks if the specific bug fix works correctly.

Comments

Software Testing Module 1

Software Testing is a process in which identifying Completeness, Correctness, Security & Quality of software product takes place. A software Tester must require a very different mindset from a developer. Software Testing means that checking software or a application to make sure that it work properly before people start using it. It helps in application to make it Reliable, Secure with user expectations for Business alignment. The developer only builds the product as per the user needs but the tester need to check or test it from user or customer point of view whether it meets needs of user or not. Software Testing is not just about finding Bugs, its about building trust, delivering excellence, values & a relation, reliable to user experience. What is Software Application? Software Application is a set of programs designed to perform a specific task for a specific user. For example web browsers, MS office, Gmail, Makemytrip and so on the list is never ended. Advantag...

Assignment-1

Assignment-1 1. What is the use of Six Sigma certificate? Ans:- A Six Sigma certificate is useful for learning how to improve quality and reduce mistakes in any process—whether in software, manufacturing, business, or services. In simple words, Six Sigma teaches you how to do work in a better, faster, and error-free way . Main Uses of a Six Sigma Certificate Helps in Better Career Opportunities Improves Problem-Solving Skills Reduces Errors and Waste Useful in Many Fields Six Sigma Example : A company uses Six Sigma to reduce defects and improve efficiency in its operations. 2. What is the use of ISO certificate? Ans:- An ISO certificate shows that a company or organization follows international standards for quality, safety, and efficiency in its work. In simple words, it tells customers, This company works in a proper, safe, and trusted way. Main Uses of an ISO Certificate Improves Quality of Products & Services Builds Customer Trust Helps in Getting More Busines...

Software Testing Module 3

V Model 1. Verification (Static Testing) (Left arm of V model) Definition: Verification is the process of checking whether the software is being developed correctly according to the requirements without executing the code. Like: "Are we doing the job right"? What Verification Checks Requirements are clear and complete Design matches requirements Code follows design standards Documents are correct and consistent How Verification is Done Requirement reviews Design reviews Code reviews Walkthroughs & inspections Key Characteristics Static process (no code execution) Done early in SDLC Prevents defects rather than finding them later Saves time and cost Example: If the SRS says “Password must be at least 8 characters,” verification checks whether this rule is correctly written and included in the design and code documents. Diagram: SRS (Requirements) ↓ Design ↓ Code ...

Software Testing Article

Search This Blog