In the last topic we have studied End-to-End Testing. And now we will learn about Sanity Testing. First of all, we will learn Sanity Testing introduction, example and why are we using Sanity Testing? Sanity Testing is the subset of regression testing and it is performed when we don’t have enough time for testing. We will perform Sanity Testing when the build has cleared the smoke test. Sanity Testing tests the major functionality. We will perform Sanity Testing when the development team wants to know the quick state of the product or the development team has done any minor change in the coding. So, we will perform Sanity Testing, so that we get to know that because of a small code we don’t get any major critical issues in the build. We will see with an example so that we can easily understand. Suppose there are 5 modules in a project. Login Page, Home Page, User Detail Page, New User Creation and Task Creation. And the bug is on the Login page. In the username field, they are accepting 6 alphanumeric characters, which is against the requirement. The requirement should not be less than 6 characters. And now it is accepting less than 6 characters. That means it is a bug. The testing team has reported the bug and the developer team has also fixed it. When the developer team will fix and pass it to the testing team. Then the testing team will test the other modules to see if any other functionality will get affected after this bug is fixed. We get to know that the bug is fixed but something else is stopped. And this is called Sanity Testing. Why will we use Sanity Testing? Sanity Testing is performed after retesting. There is a script for smoke testing but for Sanity Testing there is none. We learned the definition of Sanity Testing. We saw an example of different modules. There was one bug in it. It was accepting the characters. And why do we use Sanity Testing? In the next lecture we will see Smoke Testing.
Share a personalized message with your friends.