To perform Sanity testing effectively, QA should first identify the areas where changes happen and their dependencies. To do this right, QA needs to communicate with developers to understand the impact of the changes.
As Sanity testing aims to check newly implemented changes quickly, testers do not need to script the test cases. They simply execute the tests to verify the changes work as expected. Then, randomly test a few related features to verify that they are also working fine.
Sanity tests are usually used in the real world when there is a small change like a bug fix or a slight improvement of a feature. It's widely used in Agile development, which encourages changes and has time constraints to speed up the release process. Sanity testing helps reduce redundant testing efforts in those situations but still keeps the quality and meets the deadline. Example:
We already have a Search feature for the same Bird Eats Bug application that allows users to search bug reports by title, reporter, and domain. Now, users request to add a function to help them search bug reports by Jira and GitHub status via integration.
After the development team has implemented this requirement, and it is ready for testing, the tester will perform Sanity testing as below:
- Focus on this Search feature to verify that it works well with Jira and GitHub status.
- Testers will check other functionalities that are related to this change, such as the existing search by title, reporter, and the domain is working the same as before.