Forum Discussion

alibaba82's avatar
alibaba82
Super Contributor
14 years ago

XML File test step

We are starting to push soapUI towards some other teams in the company and I am finding that a lot of enterprise application rely on various configuration or trigger xml files. The idea is that once the system detects that some third party or some internal application has dropped some xml file in a designated network location, ftp, etc, it kicks off other sub systems.

As such, the QA teams in these departments write java/c#/etc code to read the xml and then test the appropriate sub systems.

Would it be possible to add a new type of teststep called XML test step ? This can read XML from a local or remote file.

I think this would help me tremendously in convincing some of the other teams into considering soapUI.

Thanks

Ali

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    You should be able to do this with the DataSource Test Step set to Directory. Targeting whatever is in a certain directory and read the file content into a property, which yuo later can assert etc.

    Let us know what you think

    Magnus
    SmartBear Software
  • alibaba82's avatar
    alibaba82
    Super Contributor
    14 years ago
    I tried this out and it doesn't seem like a very graceful way of reading or asserting on the xml content. Plus asserting on property test step using the powerful assertion wizards is not really possible. We would have to write groovy scripts to assert on property test step.

    To make a case to other teams to move away from custom python/java/C# tests and move to soapUI, I need to able to show how they can a do a lot more and doing a lot less coding.

    Ali
  • alibaba82's avatar
    alibaba82
    Super Contributor
    14 years ago
    Hi,
    Any idea if this can be implemented anytime soon ?

    It would be great if we can just use the HTTP test step for this. However, it seems like the currently the http teststep forces us to specify http:// in the request url.

    This would be a really convincing feature for me to show to other teams.

    Thanks

    ALi