Forum Discussion

sbeauvais's avatar
sbeauvais
Contributor
12 years ago

[Reg] schema load affects first request SLA

Hello.

I am using SoapUI Pro 4.6.4 and have some testsuites running through "SoapUI Pro 4.6.2 Maven2 TestCase Runner". (This reproduces with the 4.6.4 plugin.)

I noticed that the Response SLA for the first testcase that runs in every project/testsuite is excessive (500 to 1500ms higher than expected).

Looking at the execution log, I see a bunch of "[SchemaUtils] Added default schema from file..." log items between the request/response and the assertions of the first testcase. See attached file.

I suspect that these schema loads are affecting the calculation of the Response SLA. I would consider this a bug. Is there a way to work around this?

Currently I have to artificially increase the expected SLA for the first testcase, which is not acceptable.

Please let me know if I am doing something wrong, or how to work around this.

Sincerely,
Severin Beauvais
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Hi,

    Are you able to reproduce the same issue in SoapUI Pro 4.6.4 without using the pro maven plugin?




    Regards,
    Marcus
    SmartBear Support
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    Yes, this issue reproduces if I run the tests from the command line (testrunner). See attached.

    (I'm using a snapshot version as there is a fix in there I need... waiting for 4.6.5!)
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Hi,

    Can you check that your project has "Cache Definition" set to true in the Project properties tab in SoapUI Pro?





    Regards,
    Marcus
    SmartBear Support
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    I do not see a Properties tab on the project page.

    Did you mean the WSDL Settings tab under Preferences? On this page, the 'Cache WSDLs' option is enabled.

    I can also confirm that the project XML file contains a embedded copy of the WSDL.

    However, as seen in the testrunner logs, the WSDL is explicitly loaded anyway.

    SB
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    Oh, hum... When running through testrunner or the Maven plugin, no settings file is used. Therefore, the "cache" setting is defaulted (I assume, off).

    I will configure things to use a settings files with the required cache setting and see if that works as I need.


    SB
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    OK, I have not yet configured a settings file for my Maven run, but I noticed in my CLI testrunner run (output attached above) that my personal settings file is used, i.e.,

    10:46:31,553 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\SeverinB\soapui-settings.xml]


    This settings file definitely has the cache setting enabled, i.e.,

    <con:setting id="WsdlSettings@cache-wsdls">true</con:setting>


    And yet, as described above, the WSDL file is explicitly loaded when the test starts.

    Back to you.


    SB
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    Please check if "Cache Definition" is set to true for the project. I've attached a screen shot.




    Regards,
    Marcus
    SmartBear Support
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    Thanks for showing me where to look for this. Yes, all projects have Cache Definitions = true.

    By the way, I have now configured the use of a settings file for the Maven runs, but I still see all the schema additions (WSDL load) in between the first request/response and its assertions (the subject problem).


    SB
  • sbeauvais's avatar
    sbeauvais
    Contributor
    12 years ago
    After changing directory to the SoapUI bin folder, I enter:
    testrunner.bat -r "h:\pcss-testing\PCSS Civil\PCSS-Civil-soapui-project.xml" -t "h:\pcss-testing\soapui-settings.xml"