michaelmerrill
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Property Transfer Steps in my jenkins job that runs the maven plugin always fails.
I printed out the error message the the PropertyTransferTestStep result, and it appears to be an issue with the XML libraries. 14:45:50,013 ERROR [log] Error from test step: com.eviware.soapui.impl.wsdl.teststeps.PropertyTransferException: error: Unexpected element: CDATA1.3KViews0likes2CommentsRe: Property Transfer Steps in my jenkins job that runs the maven plugin always fails.
This is the groovy step that runs our test steps: def apiTestSuite = testRunner.testCase.testSuite.project.getTestSuiteByName("apiGatewayTest") for(tcase in apiTestSuite.getTestCaseList()) { if(!tcase.isDisabled()) { log.info("running test case ${tcase.name}") for(tstep in tcase.getTestStepList()) { if(!tstep.isDisabled()) { log.info("running test step ${tstep.name}") status = tstep.run(testRunner, context).status log.info("test step status is ${status}") if(status.toString() == 'FAILED') { testRunner.fail("${tstep.name} Test failure") } } } } }1.3KViews0likes0CommentsProperty Transfer Steps in my jenkins job that runs the maven plugin always fails.
Hello, no matter what, the property transfer step for our tests always have a FAILED status. We do not see any stack traces. We are using 4.6.1 version of the maven plugin for SOAP UI. We are running the maven command through jenkins. We tried adding the net.sf.saxon dependencies, and that did not work. We didn't see any stack traces in the first place though. Our property transfers are taking the output of a json response from a previous step, and transferring that to a project level parameter. Any help would be appreciated.1.3KViews0likes5CommentsRe: Problem with new Ready API 1.6.0 and invoking tests from other projects
This ended up being due to the new install of 1.6.0 removing the customer jars I had in bin/ext. Once I put those back in, it worked again. There was a series of tests that were being ran, and the last test was a groovy test step that did the prompt. One of the previous steps did a JDBC invocation, but the driver (Oracle) was removed, so that failed, and the rest of the tests did not run. It might be good to keep jars that are not part of the standard install inside the bin/ext directory for future upgrades.1.1KViews0likes0CommentsProblem with new Ready API 1.6.0 and invoking tests from other projects
Hello, With the new version of Ready API (1.6.0), when one test step invokes another test step using groovy, the invoked test step does not run com.eviware.soapui.support.UISupport.prompt function. For instance, this method calls a test in another project: project =testRunner.getTestCase().getTestSuite().getProject().getWorkspace().getProjectByName("GLOBAL_LIBRARY") testSuite = project.getTestSuiteByName("LIB") testCase = testSuite.getTestCaseByName("Environnments") testCase.run(new com.eviware.soapui.support.types.StringToObjectMap(), false) The test step "Environnments" has this groovy definition, but the prompt does not work when invoked from the above groovy script. Note that the groovy script is in a different project. ResultEnv = com.eviware.soapui.support.UISupport.prompt("Select an Environment", "Test Environment", ['Devloco', 'DevSandbox', 'DevLab', 'Devint1', 'Uie3', 'SysTestA', 'SysTestB', 'FAT1','FAT2','Training', 'Preprod','Production','Prod_Flow_Simu_SysA' ])Solved1.1KViews0likes1Comment