Day 3: Begin reading an API testing related book and share something youāve learnt by day 30
My suggestion for this book is one that I bought over a year ago because I was moving to a company where I would be testing more at the API layer. I have never finished it but what I did learn when I started reading it was incredibly useful for my role at the time. So, Iām going to try read it to the end now. Itās āAutomating and Testing a REST APIā by Alan Richardson.
Iām going to sit this part of the 30 days out, as it feels like you guys are already reading potentially the best book out there for this
If you all feel like you learned a lot from it, Iāll look to make a recommendation to get it added to our library at work. Hopefully itāll make a great addition to our resources!
In an effort of not increasing the amount of books I currently have in my backlog I thought of reading through Katrina Clokieās API, Web Services & Microservices Testing Pathway. It gathers a lot of resources on API testing and itās been on my radar for a while so 30 Days of API Testing is a great opportunity to read all of it.
Iāve started to read āAutomating and Testing a REST APIā by Alan Richardson.I agree with other participants of the challenge - this book is a good choice. Actually Iām impressed by Alanās manner of explaining difficult technical details with simple words.
I too went with Alan Richardsonās book. I am VERY excited about it, as I have reached a very high level of curiosity about this stuff, and this book does not leave anything out.
Edit: Just throwing this out there, today on November 5th.
Alanās book is 273 pages.
If you want to read it in 30 days, that is about 9.1 pages a day if you start on the 1st. So round that up to 10. That means today you should be on page 50.
If you start today, from page 1 you should read 10.92 (say 11) pages a day to be done by the end of the month.