Review
In this chapter, we looked at developing an initial test suite and a test strategy for the Cards project. We started by looking at at the system architecture and deciding at what layer we should test. We then looked at features to test, prioritizing based on:
-
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 or parts that use third-party code you don’t quite trust
-
Problematic—Functionality ...
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