Contributions
Re: Difference- Port in Mockservices vs Mock Port in SSL settin?
I am also getting the "Address already in use" error Every time I close and reopen the soapui and start the mockservice I get the error. I tried usingdifferentports and the error reappears. I also checked the open ports using netstat. Before starting the mockservice the port is not used by any processes. Once I try to start the mock service I get the error "Address already in use" . When run the netstat again I see that soapUi is the process that is using the port2.6KViews0likes0CommentsRe: Error in loading groovy class with maven plug in
Thanks for the response. With the soapUi-maven-plugin , for free version the Script Library files were not getting added. Another work around I was able to do is to use the soapUi-pro-maven-plugin , added the script library path in the tag <con:setting id="Script Library"></con:setting> Let me explore more to see if there is an option to load it using soapUi-maven-plugin with out using jar1.6KViews0likes0CommentsError in loading groovy class with maven plug in
Can you please let me know how I can load the groovy libraries through the pom file so that my scripts can work fine. i am using soapUi version 4.6.1 and soapUi-maven-plugin 4.6.1 Below is the details of the issue I am facing I have created a groovy class file which is placed in the the <soapui installation folder>/bin/script My soapUi test cases are referring to the functions inside the class library. Scripts are working fine and I am able to execute them from test runner also. Now I am trying to integrate the soapUi scripts with maven. When I execute the scripts through maven, I am getting the below error. Error:org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script1.groovy: 1: unable to resolve class scripts.testLibrary @ line 1, column 17. def testClass = new scripts.testLibrary() ^ org.codehaus.groovy.syntax.SyntaxException: unable to resolve class scripts.testLibrary @ line 1, column 17. at org.codehaus.groovy.ast.ClassCodeVisitorSupport.addError(ClassCodeVisitorSupport.java:148) at org.codehaus.groovy.control.ResolveVisitor.resolveOrFail(ResolveVisitor.java:229) at org.codehaus.groovy.control.ResolveVisitor.resolveOrFail(ResolveVisitor.java:239)2.3KViews0likes3CommentsFind if the current test case is the first one in testrun
Is there a way to find out if the current test that is being executed is the first test case of the test run. Context : We might be executing either a test case or a test suite or the complete project. Irrespective of how we execute, we want to do a particular set of action only once during the test run from the first test case of the test run. (Like create a file to log some key details from the execution)617Views0likes1CommentRe: Test step and assertion status using testRunner.results
Thanks Michael. Step response is correct..The issue that i am having is in getting the status in the Step Finish Can you please have a look at the script log, which I am printing from the step Finish. Its not matching with the real result. What I am trying to do is to Report the status at the end of Test case. (Regarding the loop : Step 3 & Step 5 are executing the same Test Step with a different input value. For the purpose of sharing , I just used a very simple script and a very crude way to set the data )2.5KViews0likes0CommentsTest step and assertion status using testRunner.results
I am trying the below code to get the status of the test step and assertions in the soapUi test case. In the test case I am doing a loop so that the same request gets executed with multiple sets of data. The issue I am facing is that for each iteration of the step result , assertion status and error message of the last instance of the step is returned. Due to this I am not able to find out if the step passed in a particular iteration or not. Is this an issue with soapUi ? attached project has a very simplified version of what I am trying to implement) for( r in testRunner.results ) { if ( r.testStep instanceof com.eviware.soapui.model.testsuite.Assertable) { log.info "TestStep [ " + r.testStep.name + " ] finished with status " + r.status for( assertion in r.testStep.assertionList ) { log.info "Assertion [" + assertion.label + "] has status [" + assertion.status + "]" for( e in assertion.errors ) log.info "-> Error [" + e.message + "]" } //log.info r.testStep.testRequest.response.contentAsString } } Log out put is below . For the first three lines I was expecting the assertion status to be Valid. In the response that I got assertion passed, but it looks like the status from the last iteration of the step is being returned in the code. Wed Sep 25 14:27:59 PDT 2013:INFO:TestStep [ GetInfoByZIP ] finished with status OK Wed Sep 25 14:27:59 PDT 2013:INFO:Assertion [Citi Name Match] has status [FAILED] -- [Kalesh] This is not correct. For this instance the Assertion was a success. Wed Sep 25 14:27:59 PDT 2013:INFO:-> Error [Missing token [Bellevue] in Response] Wed Sep 25 14:27:59 PDT 2013:INFO:TestStep [ GetInfoByZIP ] finished with status FAILED Wed Sep 25 14:27:59 PDT 2013:INFO:Assertion [Citi Name Match] has status [FAILED] Wed Sep 25 14:27:59 PDT 2013:INFO:-> Error [Missing token [Bellevue] in Response] I am using soapUi version 4.6.0 (Same is the behavious in 4.5.2 as well) Note : Instead of using testRunner.results , if I use testRunner.testCase.testSteps["stepname"] with in the loop , I am able to get the details correctly. But I would prefer to use testRunner.results outside the loop if it gives me the correct output3.3KViews0likes3Comments