Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to populate soap request parameters from a properties or an xml file?
    primarykey
    data
    text
    <p>I am building web service testing framework. I am doing integration testing using soap ui (not pro).I have an ant script which runs my test runner. This is how my test runner looks like : </p> <pre><code> public class GatewayIntegrationTestRunner { JUnitReportCollector collector = new JUnitReportCollector(); String path = "D:/DATA/Gateway/GWIntegrationTest_soapUI/GWIntegrationTestWksp/gateway-integration-test/src/META-INF/junit-style-test-report/html"; @Test public void runGatewayIntegrationTests() throws Exception { SoapUITestCaseRunner runner = new SoapUITestCaseRunner (); runner.setProjectFile("D:/DATA/Gateway/GWIntegrationTest_soapUI/GWIntTestStdProject/Liberate-Gateway-std-project-soapui-project.xml"); runner.getTestCase(); runner.setOutputFolder(path); runner.setJUnitReport(true); runner.run(); runner.exportJUnitReports(collector, path, new WsdlProject()); runner.printReport(0); } } </code></pre> <p>My test runner loads my soap ui project xml and and runs tests spacified in the soap ui project. My requirement is that I want to specify different request parameters to the same api at different points. Earlier, when I was doing integration testing in Java, I had these request params specified in an xml file. How can I achieve this in soapui? I tried working with properties and property transfer in soapui but did not achieve much. Depending on the location where my application is deployed, I want to modify the request data, grabbing it may be from an xml file or properties file. How can I achieve it in soapui? Thanks in advance. </p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload