Posted by: Bernard Lelchuk | June 28, 2012

Quick & easy Web Service testing using PostBin – Revisited

If you’re into testing a web API by sending Post requests, there’s one service which offers this functionality quick & easy: PostBin

“PostBin lets you debug webhooks by capturing and logging the asynchronous requests made when events happen. Make a PostBin and register the URL with a webhook triggerer. All POST requests to the URL are logged for you to see when you browse to that URL.” [Source]

I’ve revisited PostBin & repeated the Multilingual support tests with several languages (E.g. French & Hindu) and it seems to work now perfectly! 🙂
However I’ve compared the results with the web service – and the latter seems to suffer from various encoding issues – See screenshot below of French & Hindu Strings in both services.

Also, here’s a nice & easy tool for sending HTTP Requests which can be used in combination with the PostBin or similar services.
Send HTTP Tool:
There are various others similar apps – feel free to drop your recommended app here. 🙂

In order to better illustrate the use of Send HTTP Tool software & the various web services I’ve decided to add screen-shots of each service.
In the gallery below I’ve tested HTTP requests on 3 similar services:

Here are my comparison review of these services:

From all these 3 services Requestbin & Postin.rb seems to have nicer layout of data & both support the expand/hide of headers & content data.
Postbin rather seems to be more difficult to read in term of UI.

Multilingual Support:
From all 3 services only Postbin & Postbin.rb seems to support Non-English characters, while the latter suffers from various encoding issues (see screenshot below).
Thus currently Postbin seems to be the best choice for Multilingual requests.
Requestbin seems to suffer from internal error upon sending a POST request with Non-English characters (see attachment).

All 3 services seems to function very similar to another. Post bin offers a simple POST requests viewer, while the other 2 services offers extended data of header/content viewer.
Additionally, Postbin.rb offers an automatic 15-seconds page refresh which proves to be very helpful as it avoids the need to manually refresh the page upon each POST request action.

Web Services Gallery:   

Cheers & Happy Testing!

Posted by: worldpressams | August 1, 2011

Log @ your help – Guest blog post by Amit Kulkarni

AK: God please save me from this app, it crash every time I am about to finish the things.

Log: Hey, hi there! Isn’t the weather outside such a beautiful?

AK: Well, I don’t care about it. And by the way who are you?

Log: Well, sorry about that, I didn’t introduce myself. I am log – I help programmers/developers quickly understand the issue, so they can fix it quickly.

AK: So WTIIFM? [What there in it for me?]

Log: Well you will not come across these issues then.

AK: But I don’t know where do you stay, or rather how I can get help from you? You see I am not comfortable with these latest gadgets.

Log: I may appear to be a stranger but certainly I am always there with you. It is jus that you never notice me.

AK: Oh! Is it? But I am just a user and not a technical person who make out from some log or so.

Log: That is not a problem. You can help others to understand the issue and rest will be taken care by them.

AK: So what info are you referring to?

Log: Sure! Can you press this key now, yes that one, and now again this one.

AK: I already said don’t expect from me – I really don’t understand these gadgets. And yes, I really don’t want to do that exercise of pressing this/that key. Damn it!

Log: But….

Logs at your help

Oh! No. Not again. Just a few minutes back I’ve experienced a system crash and it was hard time troubleshooting it. This is seriously not my day. Well, that seems to be the problem with quite a few applications out there. You know the scenario: You are up to something important and when you’re just about to finish it, something goes terribly wrong and you lose all your work! This is so frustrating. I am sure many of you have experienced similar scenarios while writing a paper, browsing a web site or even when you are just a few more steps from completing that difficult game stage you’ve been working on for the last few hours.

When something that sort of bad happens – what is the first thing we do? We cry out loud for sure. Alternatively I’d like to see users becoming friendlier with their machines/devices and look out ways or information that they can provide to the support team in order to fix the issue they experienced.

I am a big fan of logs and whenever something goes wrong I try to analyze it in order to understand what went over here. The log indeed provides the vital piece of information that is useful for developers in order to fix the issue fast. Now it appears as if I am talking like a tester and hope that every user will do so as-well. A user who’s using an application/system may not have that sort of understanding, rather let’s put it this way – a user might never feel that need.

So here is my argument – I would like to see built-in ways of submitting application/system logs directly to the support team via the application itself. This will make it simple to the regular end-user to submit application crashes or system failures with no hassle, and on the other hand will provide essential info to the support team or the develop which will enable them to fix this issue quick and make their users happy than ever. It’s a win-win situation!

Most of the applications in the market do not have this built-in feature – however if they do I am sure it will be extremely helpful for them. The support staff will not have to bother the user too much to get more information and that means a user can breathe easily and know that by reporting such issues he/she assists the developer resolving any found issues. Alternatively, if an error occurred and the user did not report it – it might not get fixed soon, or at all.

Though I understand the cost factor involved from the companies that build applications while designing such built-in feature, however I believe that they do look at it as a one time investment. Please don’t expect your users to remember what they were doing last when the crash occurred. Integrating such a built-in feature will surely assist them providing that essential info you require to fix the issue. As a company or product owner you should avoid bothering your users too much for getting your issues fixed.

I seriously enjoy an application when I see a way of sending a feedback directly via it.

So far only a small number of devices & application companies integrated such automatic crash reporting feature. For example you can see an integrated crash reporting system on Android devices such as the Galaxy S as well as on some applications running on iPhone devices, also some application for BlackBerry do have this feature. That means that the technology is already available – however application companies & device manufactures/vendors should embrace it and implement it on their devices/ applications and make this a standard etiquette of quality and reciprocation between companies and end-users.

Yours truly,
Amit Kulkarni

Image: Filomena Scalise /

Check out my profile!

Posted by: Bernard Lelchuk | January 25, 2011

Blog hits 1,000 total views – Thank you all! :)

To my dear readers,

Today I’ve hit the total 1,000 views for this blog.
I want to thank you ALL for reading & supporting it!
I wish to keep blogging top notch content and even more frequently on 2011 and I hope you’ll enjoy reading it as much as I enjoy writing it.

Next milestone is 10,000 total views! 🙂

Please feel free to drop here your requests & questions regarding testing methodologies, tools, mobile testings & apps, techniques or any other related matters.


Image: Filomena Scalise /

« Newer Posts - Older Posts »


%d bloggers like this: