Definitions and Differences - Smoke and Sanity Testing

To understand the smoke and sanity testing first we will discuss about the Software Build..

Definition of Software Build:

If we are creating any simple software application or program then we need to create a simple executable file to run the application on any other pc or environment. For this we need to simple ‘Build’ ‘Rebuild’ the application from menu options. This step will create and executable file with the extension .exe. We use this step also for large application and this is called”build” of software to create an executable program and the process is called the “Software Build”.

Software Build Diagram

Definition of Smoke Testing:

This technique will quick check the functionality of program. Developer will direct check it while directly executed the application from source code. If any break or error is there in code that will clear visible and developer will fix at on the spot. This will save the time of QA.

This process performed after the software build. For example: Verify and confirm that application launches successfully, confirm also that the Graphical User Interface is responsive… etc.

Definition of Sanity Testing:

When software build, has been completed and reported or found issue in code are fixed or functionality has been done then to confirm the fixed issues and proposed functionality are working fine or not.

i.e. if your calculator shows that 2 + 2 is equal to 5, Then definitely you will leave the formula check for like sin 30 + cos 50.

Sanity Testing Vs Smoke Testing­:

Smoke Testing Vs Sanity Testing - Key Differences

Points to Remembers:

i.                    Smoke and Sanity testing are used to avoid the wastage of time and effort by quickly deciding the application flaw is ok or not.

ii.                  Usually Sanity Testing is called Tester Acceptance Testing.

iii.                As Smoke testing is conducted on the particular build of application so it will called the build verification test.

iv.                Best Industry practice is performed on daily bases build and then smoke testing for software application.

v.                  Sanity or smoke testing can be executed by the manually or using any automation tools

Software Testing Principle	Software Development Life Cycle	Unit Testing
Integration Testing	System Acceptance Testing	Sanity and Smoke Testing
Regression Testing	Non Functional Testing	Test Case
Test Scenario	Software Testing Rules	SQL For Software Testing
Test Case Design and Example	Test Base	Traceability Matrix
Boundary Value analysis	Decision Table in Software Testing	State Transition Definition
Use Case Testing	Testing Review	Techniques of Test Estimation
Test Plan Structure	Definition of Bug	Bug Life Cycle
Automation Testing Tools	Test Web Based Application	Software Testing Types
Software Testing Techniques	Techniques in Software Testing	Test Data
Software Testing Life Cycle	Black Box Testing	Difference between Black Box testing and White Box Testing
Smoke and Sanity Testing	Testing Methodology	Extreme Programming
White Box Testing	System Software Testing	Performance Testing
Usability Testing	User Acceptance Testing	Regression Testing
MANUAL SOFTWARE TESTING	Automation software Testing	Functional Testing

Real world scenario for,  Definitions and Differences in between Smoke and Sanity Testing. Definition of sanity and smoke testing, what is software build, use of software build, how we can perform software build step

MOBILE APPS    QTP TESTING QUESTIONS  MANUAL TESTING  ANDROID APPS