REST testing
Folks, in recent months I've been doing lots of REST call testing. I use the scratchpad of Fiddler to select and send some request lines, then look at the traffic in the inspector panes. The trouble is that my scratchpad is getting longer than a Thomas Pynchon novel, so I was wondering if others here have favourite techniques or tools for doing this sort of "playaround" REST testing, perhaps with a better way or organising your scripts -- *GK*
Re: REST testing
SOAP UI? On Sun, Sep 13, 2015 at 4:48 pm, Greg Keogh < gfke...@gmail.com [gfke...@gmail.com] > wrote: Folks, in recent months I've been doing lots of REST call testing. I use the scratchpad of Fiddler to select and send some request lines, then look at the traffic in the inspector panes. The trouble is that my scratchpad is getting longer than a Thomas Pynchon novel, so I was wondering if others here have favourite techniques or tools for doing this sort of "playaround" REST testing, perhaps with a better way or organising your scripts -- GK
Re: REST testing
Postman app is quite good. It is a chrome app Greg, I know how much you love chrome On Sep 13, 2015 4:48 PM, "Greg Keogh" wrote: > Folks, in recent months I've been doing lots of REST call testing. I use > the scratchpad of Fiddler to select and send some request lines, then look > at the traffic in the inspector panes. The trouble is that my scratchpad is > getting longer than a Thomas Pynchon novel, so I was wondering if others > here have favourite techniques or tools for doing this sort of "playaround" > REST testing, perhaps with a better way or organising your scripts -- *GK* >
Re: REST testing
> > SOAP UI? > Hmmm yes, very impressive, perhaps too impressive, like a Swiss Army knife with sledgehammers. I'll give it a bash though next week to see if a subset of the free version features does what I want. I'll let you know. And yes Joseph, you know me too well ... Chrome is OUT! *GK*
Re: REST testing
Obviously, it's a trust issue. I think you should download the source code, examine all of the code so you know it has no security/privacy issues, remove anything that concerns you and then you should be able to install Postman. Source code here: https://www.chromium.org/Home I believe there is also a project/fork somewhere where they have essentially done exactly that but the name escapes me. On Sun, 13 Sep 2015 at 16:04 Greg Keogh wrote: > SOAP UI? >> > Hmmm yes, very impressive, perhaps too impressive, like a Swiss Army knife > with sledgehammers. I'll give it a bash though next week to see if a subset > of the free version features does what I want. I'll let you know. > > And yes Joseph, you know me too well ... Chrome is OUT! > > *GK* >
Re: REST testing
> > Obviously, it's a trust issue. > No, Google's informal motto is "Don't be evil" so I would trust them with my data and my life. *GK*
Re: REST testing
Greg, On 13 September 2015 at 16:48, Greg Keogh wrote: > Folks, in recent months I've been doing lots of REST call testing. I use the > scratchpad of Fiddler to select and send some request lines, then look at > the traffic in the inspector panes. The trouble is that my scratchpad is > getting longer than a Thomas Pynchon novel, so I was wondering if others > here have favourite techniques or tools for doing this sort of "playaround" > REST testing, perhaps with a better way or organising your scripts -- GK My favourits to "play" with a web service are Curl [1] and Wireshark [2]. Proper testing deserves code. Curl is a lingua franca of online REST service API documentation - I often see example calls given as Curl invocations. Curl is a cross- platform command-line tool so it composes very well with scripts. These may also work better with your VCS than the Fiddler scratchpad (I don't use Fiddler so I wouldn't know). You can also give those Curl commands to your JavaScript front-end team on Mac and they should know what to do with them. [1] http://curl.haxx.se [2] https://www.wireshark.org -- Thomas Koster
Re: REST testing
I'm using DHC extension for Chrome for all my rest tests: https://chrome.google.com/webstore/detail/dhc-resthttp-api-client/aejoelaoggembcahagimdiliamlcdmfm?hl=en It's fantastic. On Mon, Sep 14, 2015 at 11:19 AM, Thomas Koster wrote: > Greg, > > On 13 September 2015 at 16:48, Greg Keogh wrote: > > Folks, in recent months I've been doing lots of REST call testing. I use > the > > scratchpad of Fiddler to select and send some request lines, then look at > > the traffic in the inspector panes. The trouble is that my scratchpad is > > getting longer than a Thomas Pynchon novel, so I was wondering if others > > here have favourite techniques or tools for doing this sort of > "playaround" > > REST testing, perhaps with a better way or organising your scripts -- GK > > My favourits to "play" with a web service are Curl [1] and > Wireshark [2]. Proper testing deserves code. > > Curl is a lingua franca of online REST service API documentation - I > often see example calls given as Curl invocations. Curl is a cross- > platform command-line tool so it composes very well with scripts. These > may also work better with your VCS than the Fiddler scratchpad (I don't > use Fiddler so I wouldn't know). You can also give those Curl commands > to your JavaScript front-end team on Mac and they should know what to do > with them. > > [1] http://curl.haxx.se > [2] https://www.wireshark.org > > -- > Thomas Koster >
