Testing Terminology


Sanity Testing Vs Smoke Testing? The key differences between Smoke Testing and Sanity Testing can be learned with the help of the following diagram-

Smoke Testing:- is a software testing technique performed post software build to verify that the critical functionalities of software are working fine. It is executed before any detailed functional or regression tests are executed. The main purpose of smoke testing is to reject a software application with defects so that QA team does not waste time testing broken software application.

Sanity Testing:- is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing.

Key Differences:-

  • Smoke Testing has a goal to verify “stability” whereas Sanity Testing has a goal to verify “rationality”.
  • Smoke Testing is done by both developers or testers whereas Sanity Testing is done by testers.
  • Smoke Testing verifies the critical functionalities of the system whereas Sanity Testing verifies the new functionality like bug fixes.
  • Smoke testing is a subset of acceptance testing whereas Sanity testing is a subset of Regression Testing.
  • Smoke testing is documented or scripted whereas Sanity testing isn’t.
  • Smoke testing verifies the entire system from end to end whereas Sanity Testing verifies only a particular component.

2Re-Testing Vs Regression Testing:-
Regression Testing mean repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software components.
Usually, we do regression testing in the following cases:
1. New functionalities are added to the application
2. Change Requirement (In organizations, we call it as CR)
3. Defect Fixing
4. Performance Issue Fix
5. Environment change (E.g.. Updating the DB from MySQL to Oracle)

Retesting mean to ensure that defects which were found and posted in the earlier build were fixed or not in the current build. Say, Build 1.0 was released. Test team found some defects (Defect Id 1.0.1, 1.0.2) and posted.
Build 1.1 was released, now testing the defects 1.0.1 and 1.0.2 in this build is retesting.

End to End Testing :-

  • End To End Testing is a software testing method that validates entire software from starting to the end along with its integration with external interfaces.
  • The purpose of end-to-end testing is testing whole software for dependencies, data integrity and communication with other systems, interfaces and databases to exercise complete production like scenario.
  • Along with the software system, it also validates batch/data processing from other upstream/downstream systems.
  • Hence, the name “End-to-End”. End to End Testing is usually executed after functional and System Testing.
  • It uses actual production like data and test environment to simulate real-time settings. End-to-End testing is also called Chain Testing.


Exploratory Testing :-

  • EXPLORATORY TESTING is a type of software testing where Test cases are not created in advance but testers check system on the fly. They may note down ideas about what to test before test execution. The focus of exploratory testing is more on testing as a “thinking” activity.
  • Exploratory Testing is widely used in Agile models and is all about discovery, investigation, and learning. It emphasizes personal freedom and responsibility of the individual tester.

Mr. Arshad Hussain, Assistant Professor, School of Computer Applications, Career Point University, Kota

Leave a Reply

Your email address will not be published. Required fields are marked *