Forum Discussion

fazlook's avatar
fazlook
Frequent Contributor
8 years ago

Automate REST api using TC

Hi there,   I would like your input on automating a REST api application.   I have TC and mostly using JScript but I could use C# if needed.   Our webApi is set up on Windows server 2008 and I ...
  • AlexKaras's avatar
    AlexKaras
    8 years ago

    Hi,

     

    > When do I need the https://..... and when do I need the TestSuite ? can I develop all my stuff under the API testsuite ? why do I need the first one ?

     

    The first node (https://...) is where you create just a separate requests to play with their parameters and check that they work as expected. After you are done with some given request, you can include it into some test(s) from the second node (API Test Suite). Every test case can have not only one request, but include other requests, pass data from one request to another, execute some intermediate actions via script code (e.g. check or query database) and execute assertions to verify that the expected result was obtained.

    https://www.soapui.org/rest-testing/getting-started.html may provide you with better understanding of the said above.

     

    > where at the project variable ? under preference ? how do I call it though ? #variable# ?

    https://www.soapui.org/scripting---properties/working-with-properties.html, https://www.soapui.org/scripting---properties/property-expansion.html and related help articles should help with this.

     

     

fazlook's avatar
fazlook
Frequent Contributor
AlexKaras wrote:

Hi,

 

> if I needed a clean project, should I just delete the http://....... and leave the API TestSuite ?

Yes, correct, as per my understanding. (Assuming that only 'API TestSuite' is left, but not child tests which become invalid for the new service. However, if you are going to test web service on two servers, it is a recommended approach to define a variable at the project level with the tested server address and use this variable in all your tests instead of hardcoded value.)

 

 where at the project variable ? under preference ? how do I call it though ? #variable# ?

AlexKaras's avatar
AlexKaras
Champion Level 3
8 years ago

Hi,

 

> When do I need the https://..... and when do I need the TestSuite ? can I develop all my stuff under the API testsuite ? why do I need the first one ?

 

The first node (https://...) is where you create just a separate requests to play with their parameters and check that they work as expected. After you are done with some given request, you can include it into some test(s) from the second node (API Test Suite). Every test case can have not only one request, but include other requests, pass data from one request to another, execute some intermediate actions via script code (e.g. check or query database) and execute assertions to verify that the expected result was obtained.

https://www.soapui.org/rest-testing/getting-started.html may provide you with better understanding of the said above.

 

> where at the project variable ? under preference ? how do I call it though ? #variable# ?

https://www.soapui.org/scripting---properties/working-with-properties.html, https://www.soapui.org/scripting---properties/property-expansion.html and related help articles should help with this.

 

 

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    8 years ago

    Hi,

     

    I am also trying to learn SoapUI and your questions are a good reason to do this. :)

     

    > What does that mean ?

    I am not sure. I never ran SoapUI tests from TestComplete, especially, using ReadyAPI stuff... :(

    It is my understanding, that there is some request in the SoapUI project and this request sends the provided json data to the server. Server responds as expected when this request is sent (manually) from SoapUI but errors out when the request (I assume as a test case?) is sent from TestComplete as a part of its test project. Right?

    Is it *absolutely the same* request used in both cases? I noted, that while all other parameters in the json are quoted, the problematic 'inactive' one is not quoted. Might it be the problem?

    Have you tried to execute the same request from SoapUI via ReadyAPI? Might it be that something happens there?

    I am not sure how to check this, but try to figure out if the same Java version is used when the request is executed in SoapUI and via ReadyAPI.

    You may post your SoapUI project to this thread so that others may try to repeat your steps if the project does not address internal service.

    One more option is to create a Support request using the relevant link on the https://support.smartbear.com/product-list/ page.

  • tristaanogre's avatar
    tristaanogre
    Esteemed Contributor
    8 years ago

    So... you need some soap to clean up your SOAP?

    sorry... couldn't resist... it's Wednesday and I needed some amusement.

  • fazlook's avatar
    fazlook
    Frequent Contributor
    8 years ago

    AlexKaras you are amazing :) I am learning a lot and that's a good thing. Despite the fact that I am an expert using test complete but I am having a problem though.

     

    {

      "id": "1",
       "name": "dog",
       "inactive": false,
       "insertDate": "2016-11-23T17:43:16",

     

    }

     

    When I run this one in SoapUI (json) , I have no problem, but when I run it from testcomplete using ReadyAPI, I am getting the following problem:

     

    ----------------- Messages ------------------------------
    [Inactive is false] Missing token [inactive: false] in Response

     

    What does that mean ? I have no assertions on that value.

  • fazlook's avatar
    fazlook
    Frequent Contributor
    8 years ago

    AlexKaras I was able to fix everything now :) Please let me know if you need any-help when it comes to integrate both SoapUI and TC.

     

    The only thing that annoys me now is that my temp folder if full of garbage from SoapUI even though I don't  have any logging. 

     

     

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    8 years ago

    Hi,

     

    Great, thank you for the update!

     

    As for the .jar-s in temp folder: it is my guess that these are remnants produced not by SoapUI itself, but by Java virtual machine (JVM) that executes SoapUI (which is a Java application). So this is out of SoapUI's control and is a problem(?) of JVM.

    I hope that either Support or someone else will correct me if my above guess is wrong.