I had great fun doing the “How to Design Effective API Tests” webinar. I don’t think we pay enough attention to test design in our test plans.
So what is it about? Once you’ve got a test plan – what to test – it’s time for the second part – the “how”.
Is it enough to check it’s returning status code? No.
It’s really deeper. About how to make sure something works. We can decide on different ways to test APIs based on the code, environment, and tools. There are many options, but some cost more. More time, effort, and reading logs – than others.
I go over considerations, along with state of mind, of how to approach API testing. What we test is important, but how we do it, might even be more.