It is just that in this circumstance, I am already a happy user of the (free) Postman API testing app, and whenever I see anyone talk about a new API testing tool, I am keen to check it out. Just to clarify my position - I run for profit web apps too, and have absolutely no objection to any developer putting a price on their products or services. We're quite biased here: many users want this feature, but we don't want to encourage bad practices (as it may be interpreted by some as "ok let's not write proper tests, there's Paw for that").Īnyway, that was to share my point of view as a Paw guy :) A robust API should have unit tests written with mocks and be part of the server code, not a few assertions made in a 3rd party app. And while we will do something somewhat related in the near future, it's a slippery slope.
INSOMNIA API CLIENT CODE
And we're writing enough code elsewhere to not want to write code in an app.Īs of scripting used for "unit" testing, we have thought about it many time for Paw. We don't want to add another level of complexity due to the tools we use.
INSOMNIA API CLIENT FULL
I know from experience as an iOS developer (then Python backend guy) that when working on a given project, our mind is already full of business logic. Because of that, we try to keep actions intuitive and keep scripting as a last resort (JS scripts & extensions are available in Paw too, btw). Then figure out what I can do to augment the weaknesses with other tools.I guess it's a matter of choice, but we see Paw as a visual tool that makes it easy to setup a request (or a set of requests) to iterate quickly when developing an API or discovering a new one. I try to identify the strengths of each tool, and the weaknesses. Proxy for capturing the traffic and helping me document my testing.Proxy for ’extreme’ payload manipulation and fuzzing.Exporting collections to insomnia for easier experimentation with requests through a proxy.Data Driven testing from data files in Postman with the Runner and csv files.I also find the JSON filtering of result payloads in Insomnia quite useful.
Burpsuite and Owasp Zap have different filtering abilities and different Fuzzers, and I like the option of switching between them all without losing testing focus and restarting the app. Often when I’m exploratory testing I’ll want to use different proxies e.g. Postman will now route traffic through a system hook proxy like Charles or Fiddler, but it can be a little more troublesome to feed Postman through a proxy, and certainly is not as easy to toggle between proxies without exiting the Postman app. I use Insomnia because the preferences dialog allows me to easily feed Insomnia through an HTTP Debug proxy like Burpsuite or Owasp Zap. Insomnia makes working with API documentation easy as well since many of the API examples are presented in cURL I can copy and paste the examples into Insomnia for experimentation. I can then copy the cURL request from Postman and paste it into the URL bar in Insomnia which does a really good job of creating a request in Insomnia. I either export my Postman collection and import it into Insomnia as a Workspace, or I convert a Request in Postman to a cURL request using the code generation facility in Postman. When I find a ’thing’ and need to explore in more detail I move over to Insomnia.
In Postman I build a collection with my main requests and examples. In this post I’ll describe, and show, how I do that. Insomnia REST for more exploratory API testing.Java and REST Assured for automating the API.Postman for interactive requirement and documentation based testing.In my recent HTTP REST API application testing I have been using a combination of tools: Insomnia makes switching HTTP proxies easier than Postman when performing exploratory testing TLDR Use a combination of tools to offset other tools weaknesses.
0 kommentar(er)
