Forum Discussion

Finan's avatar
Finan
Frequent Contributor
14 years ago

Error when performing tests via testrunner.bat

Hi,

When I run a testsuite via the soapUI gui, it runs without errors/ fails.
When I run the same testsuite via the testrunner.bat I see the following error in the log:

[exec] java.net.MalformedURLException: no protocol:
[exec] at java.net.URL.<init>(Unknown Source)
[exec] at java.net.URL.<init>(Unknown Source)
[exec] at java.net.URL.<init>(Unknown Source)
[exec] at com.eviware.soapui.impl.wsdl.endpoint.DefaultEndpointStrategy.filterRequest(DefaultEndpointStrategy.java:164)
[exec] at com.eviware.soapui.impl.wsdl.submit.filters.EndpointStrategyRequestFilter.filterRequest(EndpointStrategyRequestFilter.java:35)
[exec] at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:133)
[exec] at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
[exec] at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:76)
[exec] at com.eviware.soapui.impl.wsdl.WsdlRequest.submit(WsdlRequest.java:236)
[exec] at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequestStep.run(WsdlTestRequestStep.java:324)
[exec] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runTestStep(WsdlTestCaseRunner.java:207)
[exec] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:138)
[exec] at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:39)
[exec] at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
[exec] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
[exec] at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
[exec] at java.util.concurrent.FutureTask.run(Unknown Source)
[exec] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
[exec] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[exec] at java.lang.Thread.run(Unknown Source)
[exec] 08:43:14,785 INFO [SoapUIProTestCaseRunner] Assertion [SOAP Response] has status VALID
[exec] 08:43:14,786 INFO [SoapUIProTestCaseRunner] Assertion [Not SOAP Fault] has status VALID

But the testsuite completes without failed testcases.

The configuration of the project is like this:
Project, with property "url" (containing the endpoint for the webservice)
WebService, with endpoint: ${#TestCase#url}
-TestSuite 1
- TestCase 1 with property "url"
- TestStep 1 with endpoint: ${#TestCase#url}
-TestSuite 2
- TestCase 1 with property "url": ${#Project#env}
- TestStep 1 (run testcase 1.1) with property url: ${#TestCase#url}


This setup allows us create a default testcase with a complex flow of testcases,
And then creating a testsuite with testcases that have only one teststep which runs the default testcase with different properties.
Are the errors just logs or is something incorrect in our setup/in soapUI?

12 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    14 years ago
    Hi!

    hmm.. can you show the complete command-line invocation with all arguments, etc?

    regards!

    /Ole
    eviware.com
  • Finan's avatar
    Finan
    Frequent Contributor
    14 years ago
    This is the line I use: "C:\Program Files (x86)\eviware\soapUI-Pro-3.6.1\bin\testrunner.bat" -s "TestSuite 2" -rja -f C:\results "C:\Testen\Checklist.xml"
  • kmassagli's avatar
    kmassagli
    Occasional Contributor
    14 years ago
    I have the exact same problem.

    My issue started to occur after updating several WSDLs in the project. I saved a copy of the Project before the WSDL update, and I can run the command line on that project still. But the exception is occuring after the WSDL update definition, and a resave of the project. (The WSDL update may not be material to the issue). How do we know what URL the error is referring to? could this include the URI's of the WSDL files inside the Project file? Something else?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    14 years ago
    Hi,

    the error is related to the URL being used for a test request, and it indicates that the URL is empty!? Can you share your project (after the update) with us so we can have a look at this!?

    regards,

    /Ole
    eviware.com
  • kmassagli's avatar
    kmassagli
    Occasional Contributor
    14 years ago
    Hi Ole,
    The issue is that the Endpoint URL is not blank. Even a valid response is returned back as shown in the SOA transaction log. What seems to be problem is that a Project property is used to populate the Endpoint for the request. The property is defined in the Project-scope. When I insert a value in the property and run the request via GUI - the request works.
    However when I pass the property in via command line, it fails with MalformedURLException. It did not fail initially, but the failure seems to occur after I open the Project in Composite mode, and then save it as a flat-file, then reopen it. This seems to be a contributing factor to reproducing this defect, and gets the project into a weird state.

    I reproduced 2 runs:
    A. A Failing run (with the MalformedURLException) at 12:07pm where the Property value is passed into the command-line. The property is referenced in the SOA request endpoint.
    B. A Passing run (no exception encountered) at 12:10pm where the SOA request endpoint is hardcoded - while the property is still passed in, request does not reference the property - it is a hardcoded string.

    I have zipped and attached artifacts from 2 command-line runs:
    1. the Project itself,
    2. The output consoles
    3. SOA Transaction logs

    In hopes that you can pinpoint the issue.

    Command line used is in the consoleout logs.

    I am licensed user of SoapUI Pro
    Currently using version:

    soapUI Pro 3.6.1, copyright (C) 2007-2010 eviware software ab http://www.soapui.org | http://www.eviware.com Build dist-118-2010-10-18, Build Date 2010/10/18 15:
  • kmassagli's avatar
    kmassagli
    Occasional Contributor
    13 years ago
    Hey Ole,
    Any chance I could get this issue looked at?

    regards,
    Kevin
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    13 years ago
    Hi,

    hmm.. could you try removing the quotes around the parameter specification, ie change

    -P"ServiceEndpoint=http://cwvdv-soaora-1:8080/ServiceImpl/"

    to

    -PServiceEndpoint=http://cwvdv-soaora-1:8080/ServiceImpl/

    (do the same for the other arguments with quotes)

    Does that make any difference?

    regards!

    /Ole
    eviware.com
  • Finan's avatar
    Finan
    Frequent Contributor
    13 years ago
    FYI, the issue also occurs for projects where I do not change the project properties from commandline.
  • kmassagli's avatar
    kmassagli
    Occasional Contributor
    13 years ago
    Thanks but when I try removing the " " from the command line arguments, I get the same error.

    regards,
    Kevin
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    13 years ago
    Hi Kevin,

    thanks, I've been able to reproduce this with your files now; it seems to me that this error is actually something you can ignore - it happens when soapUI internally processes all the endpoints in the project (I'm still digging in to this), but the actual request seems to be executed with the correct endpoing (ie the one specified on the command-line). Do you have indications that this is not the case?

    regards!

    /Ole
    eviware.com