What is difference between sanity and 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.
Which test comes first smoke or sanity?
As per the requirement of testing & time availability, the QA team may have to execute Sanity, Smoke & Regression tests on their software build. In such cases, Smoke tests are executed first, followed by Sanity Testing & then based on time availability regression testing is planned.
When does smoke and Sanity testing are performed?
Smoke is performed on relatively unstable product (initial builds) while sanity is done on stable builds . Once the build passes smoke, the next step would be Functional testing and then regression testing. For Sanity, if a new functionality is added then Functional testing and regression. If there is a bug fix its retesting and regression.
What is smoke, sanity and dry run testing?
What is Smoke, Sanity and Dry Run Testing? Smoke Testing: means testing the basic function to check the product is stable or not . Sanity Testing: means testing few modules deeply to check it is bug free or not. Dry run Testing: means testing the entire product deeply i.e, checking all modules in depth to check whether it is bug free or not.
What is smoke testing and Sanity testing?
Smoke testing is a preliminary test which is used to catch the high-level functional errors of an application while sanity testing is a kind of software testing that is performed after receiving a software build with minor changes in code or functionality. Thus, this is the main difference between smoke and sanity testing.
What is an example of a smoke test?
For software purposes, an example of smoke testing could be for a hotel reservation site. In this smoke test example, the tester would ensure the user will be able to sign up, change your password, create a booking, and be notified.