API Testing

TLDR; Postman snippets can help us get started with scripting assertions to support REST API Testing

TLDR: When we use multiple tools and existing tool features, we open up new options in how we approach our testing. This can help us identify workarounds when we identify testability feature requests, and might even remove the need for the testability feature.

I set myself a Practice Test Exercise. You might want to try it yourself before reading the full text of this post.

TLDR: when I have a small set of HTTP use-cases, and I’m working on fast in-build HTTP integration verification then I’ll probably use HttpURLConnection

TLDR; Turnkey linux VM for testing Tracks using network settings Bridged, or Host Only.

I normally use VM Ware, but I create a video showing Turnkey Linux and Virtual Box to help people with the network settings.

TLDR; Use a combination of tools to offset other tools weaknesses. Insomnia makes switching HTTP proxies easier than Postman when performing exploratory testing

Is it REST? Does it matter? We have to test it anyway.

Some applications provide an API. Some websites provide an API. This post provides some information on API testing, since that appears to have consume a lot of my time in January 2015.