During patch certification process, a sanity test suite is created to verify if the existing roles/functionalities are working as intended before patch implementation.
Let's go through some of the best practices of using Sanity test suite.
1. The Sanity test suite is executed to ensure that we are able to verify the functionality of the environment in minimal possible time. Thus, it should contain test cases that cover processes of almost all the transactional screens of your testing module. The recommended approach is to have minimum number of cases containing maximum number of transactional screens.
2. Consult with your functional teams to identify the test cases that cover most transactional screens. As they have the knowledge of processes whose test cases cover almost all scenarios.
3. If your process has too many test cases (say 300-500), then you may choose to create 2,3, or more sanity suites that may cover all their processes. Then, you can run these suites parallelly to reduce time spent in sanity check of the system.
4. If you testing module contains lesser number of test cases that may be executed completely in a few hours, then you can skip the sanity suite creation process and instead run all those test cases.
5. While creating the sanity test suite, ensure that you have included dependent test cases in a single suite. For example, if you have a test case A whose output will be used in test case B, then it is essential to include them in the same test suite. If you put them in different suites and execute them parallelly, then the execution will fail even if your system is working correctly.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article