Chapter 11. Testing CDK Applications
Writing tests for your CDK application is a topic worthy of its own book. There are some great books out there on writing tests, test-driven development, and testing infrastructure. For this chapter, we will focus specifically on testing CDK applications and infrastructure using some of the unique tools that come with CDK. There is a big debate about the best way to incorporate tests into your development process. Some people say that all development should be test driven, meaning that you write your tests before you even write your application logic. While this is a good fit for some development teams, we have chosen to build our logic first and write tests second. We will leave it up to you to decide what works best for your team.
In this case, we will write two kinds of tests: infrastructure tests and end-to-end tests. Infrastructure tests will test the infrastructure that we have built using CDK—basically, we want to make sure that we are deploying the things we intended to deploy before we start creating resources. End-to-end tests will test the entire application from the frontend to the backend—we want to make sure that the inputs or user interactions with our application produce a predictable and accurate output. We will not be writing tests for our frontend application, but in the notes at the end of the chapter, we recommend some books and resources for testing frontend applications.
In this project, we will write some infrastructure ...
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