Writing a Test Strategy
Earlier in the chapter we decided that most of our testing will be through the API. The CLI will be tested enough to make sure it calls the API correctly. We’re going to punt on database testing for now. We can pick it up later if we want to have a set of tests useful for migrating to a new database package.
Even with this quick summary of our testing strategy, it’s easy to forget the details once we are in the thick of testing. Therefore, I really like to write a testing strategy down so I can refer to it later. Writing it down is especially important if you are working with teams, even if there are just two of you.
Here’s the current Cards testing strategy:
-
Test the behaviors and features that are accessible through ...
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