![]() In Insomnia's case, I was ready to dismiss it because I read about the simplicity of the interface, and I saw a 'Pricing' link on the web page. But for me, I didn't see any solid reason to switch to Paw from Postman unless I came across an absolutely killer feature that I could not live without. It sounds a great product and is well worth the money. However, if the other product is a 'paid for' product, then it has to be VERY compelling indeed to make me switch from the free one I am already using.įor instance, I (and many others) think that Paw is worth the licence fee. 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. 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. 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). "Keep It Short and Simple" - Take your time.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. List any troubleshooting steps you've already tried, or temporary fixes you've discovered.įor a detailed "coaching", please see the User Tips Help us to help you on these forums and Writing an effective Apple Support Communities question.Describe the problem, and include any details about what seems to cause it.Provide the version numbers of your operating system and relevant applications, for example "OS X 10.4.11" or "Safari 4.1.3".Please do not include your Serial Number, IMEI, MEID, or other personal information. Include your product (device) name and specs such as processor speed, memory, and storage capacity.To help other members answer your question, give as many details as you can. Quoted from Apple's "How to write a good question" If this issue is new, tell us what immediately preceded its onset - add software, upgrade or update? New equipment? We need to understand everything that you know and have experienced. Tell us step-by-step, in detail what your actions are. ![]() ![]() We need much more information to give you specific help. Top right of any ASC page = NEW > Discussion You have tacked onto a VERY OLD thread = not recommended ![]()
0 Comments
Leave a Reply. |