Tag Archives: RTE


We started our journey during April 2014 and we went through lots of changes in the way we were working due to whatsoever reasons. There were boring days and at the end of the day there is no sense of accomplishment after sitting at office for 8 hours and doing something which did not make us happy. Some people joined our team initially and they left us for good. There were non-technical problems and I never wanted to spend time on non-technical part more compared to technical part of running a tech start-up. The good thing is, I always fixed the problems right-away and instructed the team to do focus on technical things, innovation and more while I take care of things that are under my control. Thereafter, we knew what we had to do collectively as a team and rock the Software Testing space.

No projects, NO BIG DEAL!

We did not have projects for many months, maybe time was the answer. Instead of cribbing about “we are not getting projects”, we said, “FUCK, let us start with some in-house projects and then started to brainstorm“. We started feeling happy and awesome about that time we spend at our startup. An idea hit us and that was, “How about open-source / freeware for software testers around the globe?” And we were like, “That’s kick-ass stuff!” Let us do it. Our rock-star developers started working on building open source apps and then we started to release them under MIT license. We do not like * (conditions apply) when its open-source / free.

Our team-members & contributors

We kick-started our journey with our first utility developed in python and that was HCE (HTML parser / HTML comment extractor). It was developed by our C, Python, and Java programmer Sandeep Tuppad. He loves neat code and with his support, we were able to release our first utility as open-source on web.

 Test Insane - Software Testing Community Contribution 2014 and 2015

Test Insane – Software Testing Community Contribution 2014 and 2015

Later, it was a surprise when our rock-star developer Karthik Kini (The C# and the Web guy) developed RTE (RestFul Test Endpoints) and said, “Hey Santhosh, here is something I have developed and we can offer as micro-service to the world which could help developers / testers to test”. And I was like, “INSANE”.

And the BIG thing of 2014 was on the way and that was an idea about “Developing software testing mind-maps and uploading them on our own platform of mind-maps repository”. Karthik Kini being the Web Guy was agile in developing the platform and then we invited / requested testers around the world to contribute. Today, we have 100+ mind-maps and 16+ contributors who develop the testing mind-maps and then we upload them in MindMaps repository.

What’s up with 2015?

We have realized that, it is time to make MONEY now & we halt these activities it is not ONE TIME activity, but a journey where we keep contributing to the Software Testing community. The simple reason is, we love the journey of being happy in our life and contributing to the testing community in terms of open-source apps, freebies makes us feel insanely happy!

Watch out for more in 2015! We are going to explode enormously in 2015 in terms of community contribution.

Follow @testinsaneapps to keep up with the insane updates. We don’t mind if you want to follow our Facebook page as well.

RESTful Test Endpoints – Test The Unexpected Behavior

RESTful Test Endpoints Representation

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 http://apps.testinsane.com/rte/ 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 welovetohelp@apps.testinsane.com.