Evaluating the Features to Test
Before we create the cases we want to test, we first need to evaluate what features to test. When you have a lot of functionality and features to test, you have to prioritize the order of developing tests. At least a rough idea of order helps.
I generally prioritize features to test based on the following factors:
-
Recent—New features, new areas of code, new functionality that has been recently repaired, refactored, or otherwise modified
-
Core—Your product’s unique selling propositions (USPs). The essential functions that must continue to work in order for the product to be useful
-
Risk—Areas of the application that pose more risk, such as areas important to customers but not used regularly by the development team ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access