Forum Discussion

Xiaodong_Qin's avatar
Xiaodong_Qin
New Contributor
16 years ago

Major issues with SoapUI 2.5.1 Pro version (Trial)

I am evaluating SoapUI pro 2.5.1 to test our restful web services.
I ran into issues and I created a bug for it:

https://sourceforge.net/tracker2/index. ... tid=737763

In summary, I ran into 2 major problems:

1. Sometimes the Source fields of The "Property Transfer" steps
    are reset to empty without any reason.

2. The xml request content is deleted with no reason if I clicked
    the tabs "Request/Raw/Outline/Form" a few times.

Please help.

6 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi!

    Thanks for your interest and for reporting this.. Are you getting any errors in the error-log when this occurs?

    We would need to reproduce to be able to fix it, do you have a reproducible setup for any of these?

    regards!

    /Ole
    eviware.com
  • Thank you very much for your prompt response.

    I did more investigation and here are the details.

    ================================
    Issues #2
    ================================
    (1) I did not see anything in the "error log".
    (2) I was able to reproduce the problem easily this morning
        after trying a few times.

          It looks like the trouble maker is the "From" tab for xml request.
       
          I pasted an xml content to the "Request" tab, I did not use
          "From" tab to import any xml file, thus this tab is empty.
          Then I clicked "From" tab and went back to the
          "Request" tab, the xml content pasted in the "Request" tab
          was gone.

          This is definitely a very strange behavior. I would assume
          it can be easily reproduced in your test environment as well.

    ===========================
    Issue #2
    ===========================
    I am not sure what happened, if I edited a few test steps, ran a few test cases, sometimes the "Source Step" became empty, causing the test failure.
    It is less severe than issue #2, but definitely very annoying.

    Those 2 issues are the major reasons that prevent us from
    purchasing the licenses. Since the SoapUI 2.5.1 has just been
    released, I am wondering how well it is adopted in the community now.

    Thanks again for your quick response!

    Xiaodong
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi,

    Thanks for the details. Are the values in the pasted XML visible in the Form editor? If not, are you sure the message is compliant with the schema of the request? Maybe you could attach the WSDL and the request you are trying to paste so we can try to reproduce?

    Maybe you could also try the latest nightly build (www.eviware.com/nightly-builds) to see if it fixes any of these issues!?

    regards!

    /Ole
    eviware.com
  • Hi, thanks for the follow up.

    More details on the project I tried out.

    We are developing REST web services. So no WSDL file.
    Since our web service hasn't supported WADL yet,
    for the SoapUI project, I had to manually add web service
    and resources to SoapUI, while SoapUI did generate the
    WADL file nicely for me.

    I tried more on the "Form" tab, here is my observation:


        (1) The pasted xml content in the "Request" tab
              is not visible in the "Form" tab at all.

        (2) "Form" tab does allow the importing/loading of the xml request
              file. I imported the xml request file, which is
              the same content as I pasted to the "Request" tab.
              the "Form" tab's main area does not indicate anything
              of my newly imported file. It remains empty.
              I have no idea of what the main area is trying to show.

        (3) I can only see the xml request file in the "Attachments"
              tab below.

        (4) I pasted the xml request to the "Request" tab, I clicked
            the "Form" tab, the content in the "Request" tab is gone again.
            This indicates something wrong in the coordination of the tabs
            "Form" and "Request".

        (5) The name "Form" is not very meaningful. I have no idea
              of what it is trying to do, I initially misunderstood it as "From",
              which might make more sense since "From" might mean "Importing".


    Another comment on the usage of the "Property Transfer". I noticed
    that given an xml request, the "Outline" tab allows the selection of
    the menu "Transfer from". I made some property transfers, but the "Outline"
    tab does not have visual clue to what xml elements have been made property
    transfer. If SoapUI can add any visual indication of those elements that
    have been done for property transfer, that will be great.

    I need to check with my team lead to see if I can send you the soapui
    project I have been working on. I will keep you informed.

    Thanks a lot!

    Xiaodong
  • Dear eviware support:
    My team lead has approved that I can send you the SoapUI project
    I worked on. See the attachment.

    Please look closely at the "returnInitiation" test step,
    the xml request is pasted to the "Request" section.
    If you click the "Form" tab, the content will be gone.

    Let me know if you will be able to reproduce the problem.

    Thanks again for your highly professional follow ups!

    Xiaodong
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Xiadong,

    thanks for all your detailed information!

    The Form editor renders a user-friendly input-form for the underlying XML based on the XML Schema definition of the corresponding message/body (see http://www.soapui.org/userguide/formeditor.html). In your case you have no such definition so the Form editor will not be able to contain anything, but it should of course not remove the XML as you describe; this looks like a bug to me. Since it doesn't really make any sense to have Form editor in this situation (ie when there is no schema) its presence is just confusing, I'll see if we can remove it altogether.

    Regarding the visualization/accenting of xml that is referenced by a property transfer or property expansion, this is a great idea; I'll add to our (ever growing) list of planned improvements..

    Hope the above makes sense, thanks for taking your time to point this out. I'll post back when this has been fixed / handled in a better way.

    regards!

    /Ole
    eviware.com


    I