Forum Discussion

Peter_Liljenber's avatar
Peter_Liljenber
Occasional Contributor
16 years ago

SoapUITestCaseRunner SchemaCompliance Assertions

Hi,

While running SoapUITestCaseRunner with out tests we notice that the "Schema Compliance" assertion isn't regarding the -h flag.
Is this the correct behaviour? Since we're developing tests on our localhosts and running the tests on different hosts we use the -h flag to set which host to make the calls on.
The schema compliance assertion points to a WSDL definition and it would be preferable if the URL was substituted just as the request endpoints.



  http://:/services/PortType?wsdl

4 Replies

Sort By
  • omatzura's avatar
    omatzura
    Super Contributor
    16 years ago
    Hi,

    you are right, this is not supported.. you would need to use a property-expansion to achieve this, for example set the endpoint to "${#System#my.wsdl.endpoint}/services/PortType?wsdl" and then add -Dmy.wsdl.endpoint=... to the testrunner invocation..

    regards,

    /Ole
    eviware.com
  • Mirvnillith's avatar
    Mirvnillith
    New Contributor
    15 years ago
    So there is no simple, built-in way to just use the cached WSDL within the project?
    That would be the most common thing as I see it ...
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi!

    if you leave the URL for the schema compliance assertion empty it will (or should at least) use the cached WSDL instead.

    regards!

    /Ole
    eviware.com
  • Mirvnillith's avatar
    Mirvnillith
    New Contributor
    15 years ago
    Unfortunately not. When we have an empty URL it always uses the cached URL, but we want to use the cached WSDL and eliminate the remote lookup completely.
    If this is not possible, then SoapUI becomes "locked" towards the server where we loaded the WSDL from and that's no good.