General description
The book is 304 pages long. The reading difficulty is low. Various images, diagrams, and tables are encountered periodically. It has the following content:
Part 1. The importance of web API testing
- Chapter 1. Why and how we test web APIs
- Chapter 2. Starting our testing journey
- Chapter 3. Quality and risks
Part 2. Developing a testing strategy
- Chapter 4. Testing API design
- Chapter 5. Exploratory API testing
- Chapter 6. Automating web API testing
- Chapter 7. Developing and implementing a testing strategy
Part 3. Expanding our testing strategy
- Chapter 8. Advanced web API automation
- Chapter 9. Contract testing
- Chapter 10. Performance testing
- Chapter 11. Security testing
- Chapter 12. Testing in production
Appendix. Setting up the API sandbox platform
Opinion
Perhaps this is still "not my" book. While reading, I never really got into its approaches, and my interest in reading after pages 100–150 dropped with each page. Probably for this reason, not much information stuck in my head.
In principle, this book is not only about web API testing, but even a little more. The author tried to present the pains and problems of testing at the architectural level, so that later each layer of the architecture could be tested in one way or another.
On the one hand, this is a big plus in terms of structuring and standardization. On the other hand, this approach is only suitable for large and very large projects. For small and even medium-sized ones, much of what is described in the book is optional.
What else is characteristic of this book is that it presents a considerable list of various tools for solving certain testing and analysis tasks. But, again, on the other hand, none of these tools, be it browser developer tools or Swagger, are analyzed in detail – only superficially.
However, perhaps this is not a disadvantage of the book, because if the author examined each tool in detail, the book would turn out to be huge.
