Browse Prior Art Database

Quick REST

IP.com Disclosure Number: IPCOM000238070D
Publication Date: 2014-Jul-30
Document File: 4 page(s) / 372K

Publishing Venue

The IP.com Prior Art Database

Related People

Trilokesh Barua: AUTHOR

Related Documents

148378: IP.COM

Abstract

Quick REST defines itself as a framework, which capable of quickly create your automated test suite for REST services with very minimal code or without writing a single line of code at all. Treating each services as toy building bricks (Lego Blocks).

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 4

Quick REST

Abstract:

Quick REST defines itself as a framework, which capable of quickly create your automated test suite for REST services with very minimal code or without writing a single line of code at all. Treating each services as toy building bricks (Lego Blocks).

Plot:

The intent of this invention is to facilitate the testing and automation of RESTful apis at once. To test/automate RESTful test scenarios typically, we create a test-suite and then write many lines of codes to exercise the functionality. Then performance test suite to carry out performance and load test.

Particularly, being tester/QE, need to put effort and time to design automation test suite for every new offering/project along with the creation of tests data. Then there is always maintenance is associated which grows and number of automation coding and testing complexity increases.

So here the focus is to minimize the effort/thinking of creation of test- suite, what if we just only need to focus on creating test scenarios and test data. And automation test-suite is ready at once.

Primary focus is towards the responsible testers/automation testers. It can also be extended to particular Developers, Product Managers, Business Analysts etc. who are involved and responsible for delivering Restful api's.

As I have mentioned above, we typically do the following steps while testing or writing any automation tests for RESTful apis -


- Write the client code for the Api

- Define the test inputs

- Invoke the web-service/Api using the client code.

- Parse and verify the actual response is the expected response or not.

Now, if take out the all the time consuming steps and put together in one place and expose as the service. Then by consuming the above service and feeding just the input data automation is ready at once.


Page 02 of 4

The above forms the core part of this idea. The other highlight is taking advantage of the RESTful api documentation like swagger. These will enhance/easy the job of creating/defining testing scenarios as well.

Proposed Solution:

We wi...