RESTful Test Endpoints – Test The Unexpected Behavior

We were testing a mobile app which had various APIs, and now our test idea was to test for; “How does our app handle various endpoint responses like 400, 404, 500 and others apart from 200 OK status message?” Example: If you were testing a web application and you see 500 Internal Server Error with some other details and then you report it to the developer, and then the developer reverts to you saying, it is working fine now and he / she is not able to reproduce it. Then, you refresh the 500 Internal Server Error Page, unfortunately or fortunately it works! Now, you keep on trying for many hours to see that message, but you don’t! This was the problem that we were facing and we came up with the idea of developing our own API(s) which could help us to test for endpoint responses while we simulate different types of endpoint responses forcibly in order to see how our app code handles it. Note that, this can be used for Web Application Testing or Mobile App Testing or wherever you want to know how endpoint responses are handled by your app code. We just used Mobile app as an example to help you understand the context.

Where it can be used?

Prototyping : During early stage of your app development where you do not have LIVE API or Server, you could run these kind of tests to get the early feedback of how your app handled such scenarios.

Unit Testing: It can be used by developers who can call our APIs to test various scenarios.

Check Automation: You can call our APIs with different HTTP status codes like 500, 404, 400 etc. to see how your app code handles these things so that you are sure, what will be displayed to your users / customers.

Last, but not least; you can use it wherever you see the need or an idea.


RESTful Test Endpoints Representation

RESTful Test Endpoints Representation Representation

Visit RET’s page at for more details.

We Love To Help

If you face any difficulties in using it or if you have any ideas, please feel free to share with us and we can work together in building something and giving back to the community if there is a mutual interest. Write to us at

7 comments on “RESTful Test Endpoints – Test The Unexpected Behavior

  1. This is insane!

    I saw this on Facebook and decided to take a look. After quickly browsing, I decided to talk with a programmer about the potential of this tool in our work. As I write this, we are brainstorming different ways how RTE will help us during app development. We’ll pilot with one mobile app, analyse results, and most likely extend to other projects (including web).

    Thanks a lot for the idea and making the solution public!

    Best regards,

    • Thank you very much brother Jari for your insane comment! We are happy to see that you want to do pilot with one of the mobile app. If you have any feedback to make the utility better, please let us know and we will have it in our product backlog. Lots of love :-) Take care!

  2. This is something great. helpful more !

    Thank you

  3. Santosh, How is it different from mocking the API or create a stub which send all the HTTP Status response?

    Am I missing something?

    • You can definitely use mocking framework like webmock for Ruby or generic stub server like Stubby, but they have their own config, syntax etc. This is just couple of endpoints, easy to remember & use, Anyone can use this :) For instance, Quiet a few devs (Web UX, Mobile etc) don’t have any knowledge of API development or any server side tech, but they know data. This gives them endpoints to use that data and build & test their work as they develop.

    • Hey Akash, thanks for your comment from UK :-) Karthik has developed this and he explains it in his comment! Take care!

Leave a Reply to Akash Jain Cancel reply

Your email address will not be published. Required fields are marked *