What is smoke testing and sanity testing with example?

Smoke testing means to verify (basic) that the implementations done in a build are working fine. Sanity testing means to verify the newly added functionalities, bugs etc. are working fine. 2. This is the first testing on the initial build.

What is smoke and regression testing?

Smoke Testing is the Surface Level Testing to verify stability of system. Regression Testing is the Deep Level Testing to verify the rationality of system.

What are smoke test cases?

Smoke tests are a subset of test cases that cover the most important functionality of a component or system, used to aid assessment of whether main functions of the software appear to work correctly.

Is Sanity testing same as regression testing?

Sanity Testing is performed to check the stability of new functionality or code changes in the existing build. Regression testing is performed to check the stability of all areas impacted by any functionality change or code change.

What are regression test cases?

Regression testing is a type of software testing. Test cases are re-executed to check the previous functionality of the application is working fine, and the new changes have not produced any bugs. Regression testing can be performed on a new build when there is a significant change in the original functionality.

Is smoke and sanity testing same?

Smoke testing is done to measures the stability of the system/product by performing testing. Sanity testing is done to measures the rationality of the system/product by performing testing.

What is the difference between smoke testing and sanity & regression testing?

Smoke testing is executed at the initial stage of SDLC, to check the core functionalities of an application. Whereas Sanity & Regression testing are done at the final stage of SDLC, to check the main functionalities of an application.

What is the difference between sanity & regression testing and SDLC?

Whereas Sanity & Regression testing are done at the final stage of SDLC, to check the main functionalities of an application. As per the requirement of testing & time availability, the QA team may have to execute Sanity, Smoke & Regression tests on their software build.

What is smoke testing in software testing?

Smoke testing aims to reject a badly broken build in the initial stage so that the testing team does not waste time in installing & testing the software application. Smoke testing is also called as Build Verification Test. Let’s see a simple example where you are given an email application to test.

Which test cases can be set as smoke tests?

A subset of the regression test cases can be set as a smoke test. A smoke test is a number of test cases that establish that the application is stable and all major functionality is available and works. Smoke tests are often automated, and the selection of the test case is broad in scope.