Forum Discussion

jz1's avatar
jz1
Occasional Contributor
6 years ago

SoapUI Pro reports for on same test case executed multiple times in a loop

Hi,   I have a test case that is executed in a loop.  The test execution is invoked from Groovy script with different input parameter to the test execution.  When I used the SoapUI Pro reporting,...
  • jz1's avatar
    jz1
    6 years ago

    Nastya_Khovrina 

     

    The following article shows how to log test results through test case teardown.  All credit goes to the author of that article.  The CSV file created concactantes all the result runs from repeat execution.  The code worked as is and I just made some modification in passing some input parameters that indicates names of tests (from Excel) to be logged in the result sets.  If anyone is insterested I can post it here.

     

    https://dzone.com/articles/how-to-achieve-csv-reporting-in-soapui-open-source-1

jz1's avatar
jz1
Occasional Contributor

HimanshuTayal 

 

Thank you for your recommendation.  I also wrote Groovy scripts to capture the request and response data.  However I really like the reports produced by SoapUI Pro.  This is the main reason our company upgraded from SoapUI OS to Pro.  This will be a nonstarter for us for using SoapUI Pro going forward if the reporting features can not meet our requirements.  

HimanshuTayal's avatar
HimanshuTayal
Community Hero
6 years ago

Hi jz1 ,

 

I am not a Smartbear employee if you have any concern you can contact smartbear team or Nastya_Khovrina  can help you solving your problem.

 

  • Nastya_Khovrina's avatar
    Nastya_Khovrina
    SmartBear Alumni (Retired)
    6 years ago

    Hi jz1,

     

    We have a similar request in DB to treat each DataSouuce Loop iteration as a separate Test Case. Also, see this topic: https://community.smartbear.com/t5/SoapUI-Pro/In-HTML-report-actual-test-case-count-is-not-properly-displayed/m-p/182118/highlight/false#M41605.

     

    For now, I can propose the following workaround:

    You can use the RunTestCase test step and use the "Data export for automation" report type of the XML format. You can select to export all results. When using TestRunner, you can select the following parameters: 
    -a "-RData Export" -FXML

    When using these options, TestRunner will create a bunch of .txt files for each test step with the number of an iteration in the file name. For example, the "TestSuite_DataSource-TestCase_2-REST_Request-4-UNKNOWN.txt" file will contain the results of the fourth execution of the REST Request test step in a loop. In addition, testSuiteResults.xml will be created with the results of every test step execution. The <result> element in this report contains the <fileName> element with the name of the corresponding .txt file, so it's possible to see how many times the step was executed within a DataSource loop.

    • jz1's avatar
      jz1
      Occasional Contributor
      6 years ago

      Hi Nastya_Khovrina 

       

      Thank you for the recommendation.  

       

      Actually before seeing your reply, I've added Groovy scripts in the teardown section of the test case to capture the running log. It's working well for me.  Thanks for the recommendation.  I will give it try.

       

      John

      • Nastya_Khovrina's avatar
        Nastya_Khovrina
        SmartBear Alumni (Retired)
        6 years ago

        jz1,

         

        Can you share your script with Community? This can be helpful for other people!