Hi Ole, I have definitively switched to v2.0 + fix since Jan. 2nd and have not face any problem. Is that fixed soapui-pro-2.0.jar now part of the official soapUI v2.0 version download or new installations that will require that fix will still need to patch the downloaded version with the fixed soapui-pro-2.0.jar you provided ?

Thanks.

Hi, I'm seeing this error in the soapUI.log while executing the statement context.myXml = myXml  in a groovy script. The error is apparently without consequence, but still appearing as an Exception with the following Exception stack. I have verified that myXml is not null.

Is there a way to get rid of that error ?

Thanks a lot.


12:05:09,328 ERROR [SoapUI] An error occured [java.lang.NullPointerException], s
ee error log for details
java.lang.NullPointerException
        at java.util.Properties$LineReader.readLine(Unknown Source)
        at java.util.Properties.load0(Unknown Source)
        at java.util.Properties.load(Unknown Source)
        at com.eviware.soapui.impl.wsdl.support.XmlBeansPropertiesTestPropertyHo
lder.addPropertiesFromFile(XmlBeansPropertiesTestPropertyHolder.java:317)
        at com.eviware.soapui.model.support.SettingsTestPropertyHolder.addProper
tiesFromFile(SettingsTestPropertyHolder.java:118)
        at com.eviware.soapui.model.propertyexpansion.PropertyExpansionUtils.ini
tGlobalProperties(PropertyExpansionUtils.java:92)

Hi, works new with testRunner.testCase.testSuite.name.

Thanks a lot !

Hi Ole, apparently I do not have the problem anymore with your fixed soap-ui-pro-2.0.jar. I will evaluate v2.0 much further within the next few days...

Thanks a lot for the quick fix.

Hi Ole, this produces the following output:


Sun Dec 30 10:04:14 CET 2007:INFO:Initialisation Test Case in com.eviware.soapui.impl.wsdl.WsdlTestSuite@e62df

Gives at least the correct Test Case name under soapUI 1.7.6. I'll give a try with soapUI 2.0...

Thanks.

Thanks a lot. I'll try it...

Hi Ole, thanks a lot for your great responsiveness !

Yes our code is heavily relying on Mock Responses as all our Service requests are asynchroneous.

For sure we need v2.0 (at least for the Timeout feature). So your work is important to us.

Merry Christmas to you, your team and familly.

Hi, I'm observing that a Groovy script is executed up to the end even after a testRunner.gotoStepByName(someStep);

If there an efficient way to return from a Groovy script after a testRunner.gotoStepByName() call ?   return ?


Or the only way is if() else ?

Thanks and merry Christmas !


if ( requestId.equals(contextRequestId) == false ) {
   log.info ("ERROR: received RequestId value '" + requestId + "' does NOT match RequestId value in Context '" +  contextRequestId + "'");
   // Protect the Test Case against out dated or unrelated Notifications
   //testRunner.fail("Blabla");
   log.info ("Ignoring Notification for RequestId '" + requestId + "'. Returning to step Notification Request...");
   // Transfers execution of this TestRunner to the TestStep with the specified name in the TestCase
   testRunner.gotoStepByName("Notification Request");
   
}

This code is always executed:
log.info ("Received RequestId value '" + requestId + "' matching RequestId value in Context '" + 
            contextRequestId + "'");

Hi Ole, I reproduced the error where I could not save my changes with the latest v2.0 version.  As mentioned earlier, my soapui xml repository was developped with version 1.7.6.


Here is an excerpt of the soapUi log:

   at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
   at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
   at java.awt.Component.processMouseEvent(Unknown Source)
   at javax.swing.JComponent.processMouseEvent(Unknown Source)
   at java.awt.Component.processEvent(Unknown Source)
   at java.awt.Container.processEvent(Unknown Source)
   at java.awt.Component.dispatchEventImpl(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Window.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.EventQueue.dispatchEvent(Unknown Source)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.run(Unknown Source)
2007-12-18 15:30:16,468 ERROR [errorlog] org.apache.xmlbeans.impl.values.XmlValueDisconnectedException
org.apache.xmlbeans.impl.values.XmlValueDisconnectedException
   at org.apache.xmlbeans.impl.values.XmlObjectBase.check_orphaned(XmlObjectBase.java:1213)
   at com.eviware.soapui.config.impl.MockResponseConfigImpl.getResponseContent(Unknown Source)
   at com.eviware.soapui.impl.wsdl.mock.WsdlMockResponse.beforeSave(WsdlMockResponse.java:825)
   at com.eviware.soapui.impl.wsdl.teststeps.WsdlMockResponseTestStep.beforeSave(SourceFile:711)
   at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCase.beforeSave(WsdlTestCase.java:766)
   at com.eviware.soapui.impl.wsdl.WsdlTestSuite.beforeSave(WsdlTestSuite.java:395)
   at com.eviware.soapui.impl.wsdl.WsdlProject.beforeSave(WsdlProject.java:477)
   at com.eviware.soapui.impl.wsdl.WsdlProject.save(WsdlProject.java:416)
   at com.eviware.soapui.impl.wsdl.actions.project.SaveProjectAction.perform(SaveProjectAction.java:40)
   at com.eviware.soapui.impl.wsdl.actions.project.SaveProjectAction.perform(SaveProjectAction.java:27)
   at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPerformed(SwingActionDelegate.java:92)
   at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
   at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
   at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
   at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
   at javax.swing.AbstractButton.doClick(Unknown Source)
   at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
   at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(Unknown Source)
   at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
   at java.awt.Component.processMouseEvent(Unknown Source)
   at javax.swing.JComponent.processMouseEvent(Unknown Source)
   at java.awt.Component.processEvent(Unknown Source)
   at java.awt.Container.processEvent(Unknown Source)
   at java.awt.Component.dispatchEventImpl(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
   at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
   at java.awt.Container.dispatchEventImpl(Unknown Source)
   at java.awt.Window.dispatchEventImpl(Unknown Source)
   at java.awt.Component.dispatchEvent(Unknown Source)
   at java.awt.EventQueue.dispatchEvent(Unknown Source)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
   at java.awt.EventDispatchThread.run(Unknown Source)

Hi, I would like to create some log (using log4j Logger) of my Test activity. For that I need to be able to retrieve the Test Suite ad Test Cases labels from within a groovy script.  I have looked at the javadoc of the WsdlTestCaseRunner and WsdlTestRunContext and have found nothing.

Is there a way to retrieve that Information ?

Thanks.

Hi, unless I'm missing something, the Template-Driven Testing described on paragraph 1.9.2 of soapUI v1.7.6 Project Documentation is assuming that the same Test Case Context instance is shared between all Load runs (when performing
a Load Test with 1 Thread and n Runs)

But this is not what I'm observing. For a each run, a new Test Case Context instance is created and then therefore all control data are lost (like index) between Test Case runs.

Could be that in v2.0 Test Suite (String) properties can be used to store some index or position. Until then I only see the use of some external persistent mechanism (like File or Database) to share that Information between Test Case runs (in a sequencial Load Test).

Is that correct ?

Thanks.

Hi, I have been working on soapUI 1.7.6 with no problem for the last 2 weeks or so.
Yesterday I decided to try soapUI v2.0 beta2, as I was missing some important key features that were in the new 2.0 version.

Quickly while using soapUI v2.0 beta2 I had the feeling to have to redo things several times, like if my modifications were lost. First I thought I had not saved my work correctly.

Just to confirm my feeling I have done the followings:

- On my existing Test Suite I cloned a Test step in all my Test Cases
- Did some other Grovy script modifications in some Test Cases
- Saved all open Projects
- Close soapUI

After restarting soapUI (v2.0 beta2) , all my previous modifications were gone.

Since that time I have returned to v1.7.6 which does not have this kind of issue.

I suspect  some differences in the project xml repository schema ...

Found them in version 2.0 beta2 !

Thanks a lot. Makes a great sense, but I can't find the way to define new Test Suite Properties. I can see the Test Suite properties pane, but it seems to be read only
(there is a single property which is the name of the Test Suite).
The Test Suite Editor does not provide any facility either to create new properties.
I have soapUI Pro v.1.7.6.

Sorry but I'm very frustrated !

Hi,  I want to share data between all Test Cases that are in my Test Suite.
I just found out that the scope of Context properties are only for the Test Case.

Properties can be read from file (or Database I suppose), but I want to share pre-processed data between Test Cases. Not only data directly accessed from a File.

For instance my Test Suite includes an initialisation Test Case that is responsible to prepare some list (or even things like myXML). I want to have those data to be available for each Test Case so they can be used in Groovy script to set the requests for instance.

How can this be achieved ?
Thanks a lot.