Reusable REST Requests

Question

I have a scenarios where i need to call some Frequently use REST Requests in other test cases&nbsp;&nbsp;How can i setup this , i am using READYAPI&nbsp;&nbsp;

nmrao · Answer

It is good practice that each test case is independent.Can you elaborate your use case please?

678 · Answer

sample use case&nbsp;&nbsp;Project 1&nbsp; Test Suite 1(Common)&nbsp; &nbsp; &nbsp;Login In - Test Case (Rest Request)&nbsp; &nbsp; &nbsp;Logout - Test Case (Rest Request)&nbsp;Test Suite 2 (Actual Test cases)&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp; &nbsp;Test Case (Add User - Rest Request) (Pre-Requisite need to run above Login Request) then test case (adduser) and&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Logout Request&nbsp;&nbsp; &nbsp; &nbsp;Test Case (Delete User - Rest Request) (Same like above)&nbsp;&nbsp;&nbsp;

richie · Answer

Hi,&nbsp;erm - I don't know if I'm looking at the question from the wrong perspective - but it's reminding me of a question one of my colleagues asked me.&nbsp;They were looking at setting up SoapUI using their experience of setting up a front end automation frameworks - e.g. modular/test library automation framework where you have lots of 'scripts' doing&nbsp;actions/navigation through an application which then makes up a larger testcase.&nbsp; Are you considering your question from a similar perspective?&nbsp;Someone's bound to know more than me - but as far as&nbsp;I can tell, SoapUI doesn't really lend itself to modularizing a test case built from other testscripts like this.&nbsp; Just because you need a login (and perhaps a logout request) to enable you to exercise the other apis for your tests - you'll just end up wrapping the test case requests testing the other api's with the login and logout request.&nbsp; What I mean by this is if you had a 'search' and 'buy' api to test you'd just create a test case like the following hierarchy&nbsp;Login REST Request
Search REST Request
Buy REST Request
Logout REST RequestOR - have I totally gone off on one and totally misinterpreted your question? :)&nbsp;There are a couple of Sample SoapUI projects available with SoapUI.&nbsp; These have something similar to above that I mentioned.&nbsp;Cheers,&nbsp;richie&nbsp;

678 · Answer

richie&nbsp;&nbsp;Thanks for reply,&nbsp;&nbsp;with your solution i need to add Login and log out on every test case&nbsp;&nbsp;and more ever my framework is such a way that all the test case is coming from excel&nbsp;&nbsp;excel rows:&nbsp;Row 1 - Test case 1 -Search RequestRow 2 - Test case 2 - Buy Request&nbsp;&nbsp;in this case what is the solution ?&nbsp;

richie · Answer

Hi,&nbsp;Essentially "yes" is the answer to whether you would need a login request on each test case - that is - as long as there are session variables in the login response you need to pass onto your subsequent requests to enable the other requests to work?&nbsp;&nbsp;How long does the 'session' (after logging in) last?&nbsp; 15minutes?&nbsp;Is there a reason you couldn't create a login request in your first test case in your first testsuite, then grab the session variables from the login response passing them to a project property perhaps and then just use these session variables for your other apis you are testing for your other testsuite's testcases so you don't bother logging in for each test and logging out after every test?&nbsp;If your 'session' lasts 15minutes - depending on your tests/network latency etc., etc. you could possibly only need to login once per execution run.&nbsp;what I mean by this is the following hierarchy&nbsp;TestSuite1&nbsp;TestSuite1&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
      TestCase1
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;'Login Request' (grab session variables and pass these variables into project or TestSuite1 properties)

&nbsp; &nbsp; &nbsp; TestCase2
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'Datasource'&nbsp;(fileContents property created)
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'Search Request' (using the session variables via the project/TestSuite1 properties, grab values from response to pass to SearchID property)
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'Properties' (contains the SearchID property from the Search Request)
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'Purchase Request' (uses project properties, SearchID propoerty and the 
${Datasource#fileContents})and final TestCase's final step would be the 'Logout Request' to close the session

etc.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;Can you be a bit more specific about what you mean by "all the test case is coming from excel"?&nbsp; I'm not really understanding what you mean.&nbsp;Are you saying the test cases have been defined in a spreadsheet?Are you saying the test data for the requests for your tests are defined in a spreadsheet?&nbsp;thanks,&nbsp;richie

Forum Discussion

Reusable REST Requests

Related Content

Reusable REST Request approach

Reusable assertions for REST error handling in SoapUI

Reusable Instructions

Operating with REST Interfaces and Requests

Reusable Classes for Dispatch Script

Recent Discussions

Sudh budh bar hshs the day of

Assert Step Not Executing All Assertions

Include external files (XML) for JDBC connection

Accessing database connection string from groovy test step

JDBC database connection pooling