HanTestOccasional ContributorJoined 11 years ago13 Posts1 LikeLikes received1 SolutionView All Badges
ContributionsMost RecentMost LikesSolutionsxsi:nil="true" makes the whole element disappear I want to send a null value using xsi:nil="true": <mccCode>5192</mccCode> <mrr xsi:nil="true"/> <nameOnCardHolderStatement>Test</nameOnCardHolderStatement> When I sent this my RAW looks like this: <mccCode>5192</mccCode> <nameOnCardHolderStatement>Test</nameOnCardHolderStatement> With the mrr field missing. When I try this with the free version it does work. Anyone? Re: Get the status of a teststep that already has been executed Unfortunately I get a Null Object Edit: I think I'll just disable the soaprequest step and then use the groovyteststep to run the soaprequest step. This works but doesn't feel like the right way to do it ;) Re: Get the status of a teststep that already has been executed The thing is that I allready runned the TestCase so I don't get why I should invoke the runner for a second time. Isn't there a way to get the result of the previous step without having to do a runTestStep()? for reporting I can use: ${=testRunner.results[testRunner.results.size()-1].status} but isn;'t there something like that in the groovyscript step? Otherwise maybe someone can help me out on hangouts so I can show the project. Re: Get the status of a teststep that already has been executed When I run this script it always logs an UNKNOWN I've also tried to use getStatus() but unfortunately this also results in an Unkown: Re: Get the status of a teststep that already has been executed This is exactly what I was looking for thank you very much! Get the status of a teststep that already has been executed I want to get the status of a previously runned teststep in a groovyscript step. How can this be done? SolvedReady Api ServiceV Deploy as WAR not working When I create a simple mockservice using SoapUI 5.1.3 and deploy this using War on Tomcat9 everything works fine. Using that same project in Ready API 1.5.0 and deploying the ServiceV as a War on Tomcat9 gives me: HTTP Status 500 - Error instantiating servlet class com.eviware.soapui.mockaswar.MockAsWarServlet type Exception report message Error instantiating servlet class com.eviware.soapui.mockaswar.MockAsWarServlet description The server encountered an internal error that prevented it from fulfilling this request. exception javax.servlet.ServletException: Error instantiating servlet class com.eviware.soapui.mockaswar.MockAsWarServlet org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:361) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:1080) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:75) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:757) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1515) java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) java.lang.Thread.run(Unknown Source) I've tried all kinds of settings but can't get it get to work. SolvedRe: Transaction Log doesn't scale enough I don't have the problem anymore using the 1.4.0-m-SNAPSHOP version. Thanks! Re: Ready! API 1.4.0 problem - DataSource file path vanishes and the file itself gets corrupted I'm having the same problem with the DataSource file path.. but the file itself doesn't get corrupted. Switched back to an older version. Transaction Log doesn't scale enough The new windows: Transaction Log / History / Compare Do not fit on my laptop screen 1366 x 768 The bottom part is not visable when the window is docked. If I undock the window and then scale it to fit the screen it is visable. Solved