Forum Discussion

richie's avatar
richie
Community Hero
6 years ago

A bit more groovy help? Populating a REST URI with Properties Set On TestCase?

Hey!   I'm currently trying to play around with some groovy snippets people have helped me with to build a REST request using parameters saved as properties on the TestCase object - but surprise,...
  • richie's avatar
    richie
    Community Hero
    6 years ago

    Hey nmrao 

     

    yeah - I'm still talking about the same thing - I'm getting boring - right? :)

     

    So - yeah - I have a REST GET API where the query parameters on the request correspond to attributes of tables.  This will be for a reference data service providing lots of different internal systems with referencedata when required.

     

    So - say I have a table called 'PersonalDetails' with the following attributes: ID, firstname, lastname, country, phonenumber and multiple records populate this table - but for now lets use the following data

     

    ID = 123456

    firstname = rich

    lastname = jones

    country = uk

    phonenumber = 07958 985 000

     

    In the system - namespace is a grouping of tables and dataset is an alias for tables - the following GET URI 

     

    my GET URI --> http://help.azurewebsites.net/api/1/{namespace}/{dataset}?queryparm1=value&queryparm2=value

     

    the RAW of the above would be as follows:

     

    http://help.azurewebsites.net/api/1/biology/PersonalDetails?firstname=rich&lastname=jones

     

    Now - cos I can't parameterize the QueryParm names (values I can parameterize, but not the names) with the OTB functionality - the only option left to me is to hardcode multiple REST requests in the Projects section of ReadyAPI! essentially hardcoding the QueryParameters.  I have 1500 tests at the moment - thats a lot of requests in my project.

     

    Hence the reason I'm trying to put something together that allows me to call the queryparms and values to build the query string of my GET request from say a Properties step.

     

    For example - if I can query the table and extract the columns and a single record's values - I can build a Properties step containing all attributes and the values and then hopefully I can build the REST requests QueryParameters from the attributes and values set in the Properties step 

     

    (OR - I can just create a single properties file at the start and load in the table attributes and 1 record's values for later use)

     

     

    I hope I've been clear - I know I tend to ramble a bit - but its to try and ensure I've been clear in my query.

     

    Thanks for providing the URL - I have questions about this - but I'll ask in a separate post

     

    Again thanks to all and Rao for helping me out so much!  I even submitted a support call to SmartBear - but they don't support groovy coding so I know they're just gonna reject my support request - but I thought it was worth a shot!

     

    richie

     

     

    • nmrao's avatar
      nmrao
      Champion Level 3
      6 years ago

      richie,

      Thank you for your patience. Bear with me, few more questions.

      1.  You like to query db and then use the data in GET call of REST. correct? If yes, then the issue which you are mentioning for REST query parameters will be an issue even to do dynamic sql query as well. Isn't it?

      2. The final objective is to compare sql query response with REST call (GET with query parameters) response. Is this understanding correct?

    • richie's avatar
      richie
      Community Hero
      6 years ago

      Hey,

       

      ok - I tried an approach aaronpliu suggested that I'd mistaken as a lot more complicated than it appears to be

       

      I followed all the instructions, setup the groovy - but the REST step is NOT inserting the Query parms (defined as properties) into the GET request.  

       

      The test case hierarchy is as follows:

       

      PropertiesStep
GroovyStep1
RESTStep
GroovyStep2

      The testcase and groovy executes fine - the 'setPropertyValue' just isn't adding the properties as query parms/values at all

       

      I have a setupscript as follows:

      // initialize a property "index" for loop
testCase.setPropertyValue("index", "0")

      The properties step holds 2 parms and values

       

      GroovyStep1 as follows:

      //setup size of properties in order to loop run
def propsList = testRunner.testCase.testSteps["Properties"].getPropertyList()
def index = context.expand('${#TestCase#index}').toInteger()
testRunner.testCase.setPropertyValue("CountOfProps", propsList.size().toString())
// setup parameter for REST step
testRunner.testCase.testSteps["RestStep"].testRequst.setPropertyValue(propsList[index].name, propsList[index].value)

      GroovyStep2 is as follows:

       

      def index = context.expand('${#TestCase#index}').toInteger()
def max = context.expand('${#TestCase#CountOfProps}').toInteger()

if (index + 1 < max) {
    // go to run step 1, here 'Groovy' name is step 1 name
    testRunner.testCase.setPropertyValue("index", (++index).toString())
    testRunner.gotoStepByName("GroovyStep1")
}
// note that your "REST" step will be added more parameters, if you just want to run "REST" step with one parameter, then you need to "remove" others or setup empty

       

      In summary - test executes, groovy steps work without reporting compilation/runtime errors - but the REST URI doesnt get generated with the parameters specified in the properties file.

       

      I thought I was onto a winner here - cos lets face it - it's someone else's groovy - can anyone point me in direction where I'm going wrong?

       

      Oh yeah - I've attached the project file wiht a single test case of the above if anyone wants to have a look!

       

      Again thanks to all -especially aaronpliu for supplying the groovy in first place (which I idiotically didn't notice)

       

      richie

       

       

      • nmrao's avatar
        nmrao
        Champion Level 3
        6 years ago
        So the above helped?