Forum Discussion

HaedenH's avatar
HaedenH
Occasional Contributor
15 years ago

SoapUI Test Scripts not running in LoadUI

Hello,

First off, I am completely new to SoapUI and LoadUI. I hope you forgive my ignorance. I tried to figure out my issue on my own before harassing the gurus but, here I am.

I did some searching on the forums and found this post: http://www.eviware.com/forum/viewtopic.php?f=12&t=5509&p=19159&hilit=soapui+test+case#p19159 which is has similar issues to what I am experiencing. However, after following the suggestions listed, my problem was still not resolved, so I am hoping that someone can provide some assistance.

Basically, I have two test cases created in SoapUI. A fetch information, and a fetch password expiration test. In SoapUI, they both work (the fetch information takes a few moments to run, whereas the password one will execute in less than 10 seconds). However, when I load them up into LoadUI, start the Project and/or Test Case and click Run Once, the test case selected will fail immediately. The website I am trying to test does require a certificate as well as a user name and password (although I believe I have these configured correctly in SoapUI - more below). Below are the steps I have attempted to take to reach a resolution... No luck so far.

Resolution attempt #1: Proxy Perhaps?
I first read that this may be caused by a proxy issue, and tried setting the Java network settings to use the proxy that I *sometimes* have to enable when connected to my company's VPN. The good news is that I no longer received the JavaFX error. The bad news is that this configuration made LoadUI run painfully slow, so I have since set that back to "Direct Connection" (haven't seen the JavaFX error since I made the switch, fingers crossed).

Resolution attempt #2: Certificate Certainty?
I had previously imported the certificate .pfx file into the Keystore in SoapUI, and entered the password in the Security Configuration tab (double click main project -> Security Configurations -> Keystores/Certificates) and verified that the Status is "OK". I have also set up Global Properties for "uid" and "pwd" - whether these help or not, I am not sure. Still works in SoapUI. Still no luck in LoadUI.

Resolution attempt #3: Error Entry
I routed the output from my SoapUI runner to a Table Log, and receive the following error:
"[[SOAP Response] error: The document is not a Envelope@http://schemas.xmlsoap.org/soap/envelope/: document element mismatch got HTML, [SOAP Response] The document is not a Envelope@http://schemas.xmlsoap.org/soap/envelope/: document element mismatch got HTML]"

So, as of now, still don't know what the issue is, and would greatly appreciate some assistance

Update: I have downloaded the LoadUI 1.0.2-SNAPSHOT and tried using that configuration.... same issue persists.

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    15 years ago
    Hi!

    hmm.. the error you are getting the tablelog suggests that the request in your soapUI TestCase is receiving an HTML page back instead of a SOAP Response, probably some kind of error page. I wonder the following;
    - do you need to set up a proxy in soapUI to get the TestCase working there?
    - do you have a global keystore set in soapUI also (in the global preferences SSL Tab) ?
    - have you associated the keystore in your project with the requests that need it (via the keystore property in the bottom left table of properties for each request step)?

    regards,

    /Ole
    eviware.com
  • HaedenH's avatar
    HaedenH
    Occasional Contributor
    15 years ago
    Thank you for your response Ole,

    Please clarify a point for me: I can run my GetPasswordExp test case in SoapUI (which sends a username and password which are stored as global variables in the project), and it returns some XML format data (example below).
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
       <soapenv:Header/>
       <soapenv:Body>
          <p39:getPasswordExpDaysResponse xmlns:p39=address-removed>
             <getPasswordExpDaysReturn>
                <endTime>2011-02-02T13:59:58.054Z</endTime>
                <error xsi:nil="true"/>
                <recordCount>1</recordCount>
                <startTime>2011-02-02T13:59:52.669Z</startTime>
                <passwordExpDays>85</passwordExpDays>
             </getPasswordExpDaysReturn>
          </p39:getPasswordExpDaysResponse>
       </soapenv:Body>
    </soapenv:Envelope>

    I assume this is what is meant by a "SOAP Response"? If that is actually an HTML page back, then that may explain a few problems...

    To address your questions for me:
    I do not believe I have a proxy set up in SoapUI - in SoapUI, I went to File -> Preferences -> Proxy Settings, and every field here is blank. I am able to hit the site URL without turning the proxy on. All that is required is a valid certificate, which I do have to select whenever I first open up the site in my browser (I am mainly using Firefox 3.6.13 and sometimes I.E. 8 ).

    In my SSL Settings tab in the Preferences window, I do have a keystore and keystore password set up, and the password is configured correctly (again, the status = OK in the Security Configurations -> Keystores/Certificates tab).

    And lastly, yes - the SSL Keystore points to the .pfx file that I have set up as a global Keystore.
    I do not, however, specify the username and password with the requests that may need to utilize it... Perhaps that is the issue? Will check into the momentarily.

    As it is now, the Test Cases that I have set up in SoapUI run with a green light, and return code that looks like XML format. I try to sync these test cases with my project in LoadUI and run them, but they fail immediately.
    Is there somewhere in LoadUI that I have to set up the SSL Keystore and/or username and password property as well?

    Again, thank you for taking the time to answer my newbie-questions.
  • HaedenH's avatar
    HaedenH
    Occasional Contributor
    15 years ago
    Ole,

    Good news! I manually entered the Username and Password values into the test cases. Not only do they still work in SoapUI, but now execute in LoadUI as well!

    I guess it makes sense that global variables aren't read into LoadUI from a SoapUI project - we are, after all, only reading in the test cases, and not the entire project.

    I hope I didn't inconvenience you too much with my little query.
    -HaedenH