Contributions
[Resolved] Dynamically set resource path of WADL at runtime
I have the following scenario: 1) Our product supports "X" number of versions for our REST API: v3.0, v3.5, v4.0, etc 2) Each version of our API has a unique WADL, where the resource path has the version of the API contained in it like so: /product/api/v4.0/..... 3) We import the WADL (say from v4.0) and create our automated tests based on it. 4) To have these same tests execute against v3.0 and v3.5, we must maintain each of these tests in a separate soapUI project, which is not only difficult (can't easily copy tests between these different projects due to the resource path difference), but also maintenance intensive (having the same test in more than one place when test needs update). 5) We currently have coded soapUI with the ability to enable/disable tests (cases and suites) based on the API version. For example, v4.0 may introduce a new resource that we can restrict so it is NOT run against v3.5 6) What we would like to do is maintain only 1 project, with the latest version WADL, and "dynamically" set the resource path at test runtime: ex: change "product/api/v4.0/foo" to "product/api/v3.5/foo", run the tests, then change to "product/api/v3.0/foo" and run the tests again 7) I've played around a bit with a RequestFilter Event, attempting to dynamically modify the version portion of the resource path like so: request.getPath() //modify path and then set it request.setPath() This does modify the path, but only for the "next" run of the test, not the current run. 8.) I'd like to know if there is a better approach/solution to the above described problem that I should be looking at. One thought was to edit the WADL in soapUI and replace the "version" in the resource path with a variable ($foo, for example) and then set this variable based on needs. Any pointers would be greatly appreciated!10 years agoPlace ReadyAPI QuestionsReadyAPI Questions4KViews0likes3Comments- 11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.5KViews0likes0Comments
Suite Order is not Maintained in Project
SoapUI Pro 4.6.4 Mac OS X When ever I change the order of the suites in a SoapUI project, save the project, and re-import the project, the suite order appears as it originally was. 1. Move a suite into a different position in the order within a project (Screen shots 1 and 2). 2. Save the SoapUI project and remove it from the SoapUI console. 3. Re-import the SoapUI project. The suite is in the same position as it originally was as shown in Screen shot 1.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes3CommentsRe: [Res]Dump File option for Request Properties is not editable
Thanks for your reply! You may wish to update your website in this regard. It instructs to use the interface level. http://www.soapui.org/Working-with-soap ... onses.html http://www.soapui.org/SOAP-and-WSDL/reference.html11 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.6KViews0likes1Comment[Res]Dump File option for Request Properties is not editable
SoapUI Pro 4.6.4 When attempting to edit the Dump File request property for a rest interface method, I found no value could be entered in the field. (See screen shot.) The other request parameters, however, were editable. Is this a bug in SoapUI or is there some other flag that needs to be flipped for this to work?11 years agoPlace ReadyAPI QuestionsReadyAPI Questions7.7KViews0likes3CommentsRe: InvocationTargetException upon opening suite frame
Yes, there were a few more lines following the line with the NPE. Sorry for not including those. Caused by: java.lang.NullPointerException at net.infonode.properties.propertymap.PropertyMapManager.addMapChanges(Unknown Source) at net.infonode.properties.propertymap.PropertyMapImpl$1.signalEmitted(Unknown Source) at net.infonode.util.signal.Signal.emit(Unknown Source) at net.infonode.util.collection.notifymap.AbstractConstChangeNotifyMap.fireEntriesChanged(Unknown Source) at net.infonode.properties.propertymap.PropertyMapImpl$PropertyObjectMap.fireEntriesChanged(Unknown Source) at net.infonode.properties.propertymap.PropertyMapImpl.firePropertyValueChanged(Unknown Source) at net.infonode.properties.propertymap.PropertyMapImpl.setValue(Unknown Source) at net.infonode.properties.propertymap.PropertyMapValueHandler.setValue(Unknown Source) at net.infonode.properties.util.ValueHandlerProperty.setValue(Unknown Source) at net.infonode.properties.types.EnumProperty.setValue(Unknown Source) at net.infonode.properties.types.DirectionProperty.set(Unknown Source) at net.infonode.tabbedpanel.TabbedPanelProperties.setTabAreaOrientation(Unknown Source) at com.eviware.soapui.support.components.JInspectorPanelImplPro.<init>(SourceFile:126) ... 37 more Also, I'm including the contents of the event handlers. However, I don't think they're the problem. TestRunListener.beforeRun def smi_test_root_dir = context.expand( '${smi_test_root_dir}' ) filePath = smi_test_root_dir + '/Reports/' fos = new FileOutputStream( filePath + 'Results.txt', false ) pw = new PrintWriter( fos ) pw.write('Test Suite Name : Test Case Name : Test Result\n') pw.close() fos.close() TestRunListener.afterStep def smi_test_root_dir = context.expand( '${smi_test_root_dir}' ) filePath = smi_test_root_dir + '/Reports/' fos = new FileOutputStream( filePath + 'Report.txt', true ) pw = new PrintWriter( fos ) pw.write("Customized message\n") testStepResult.writeTo( pw ) pw.close() fos.close() TestSuiteRunListener.beforeTestCase def smi_test_root_dir = context.expand( '${smi_test_root_dir}' ) filePath = smi_test_root_dir + '/Reports/' fos = new FileOutputStream( filePath + 'Report.txt', true ) pw = new PrintWriter( fos ) pw.write("Customized message\n") testStepResult.writeTo( pw ) pw.close() fos.close()11 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.4KViews0likes0CommentsInvocationTargetException upon opening suite frame
I am having the following problem with version 4.5.1 on Windows 7 Professional. I have a composite project with one suite that has four test cases. There are three event listener scripts and a suite teardown script. I successfully run the test cases from the suite frame numerous times. However, when I close the suite frame, and reopen it, I can no longer run the test cases as I had minutes before. Upon opening the suite frame, I receive the following message in the SoapUI log.... Thu Jun 06 10:49:34 CDT 2013:ERROR:An error occured [java.lang.reflect.InvocationTargetException], see error log for details and the following stack trace in the error log....What can possibly be changing in SoapUI by closing and reopening the suite frame? Thu Jun 06 10:49:34 CDT 2013:ERROR:java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at com.eviware.soapui.support.components.JInspectorPanelFactory.build(JInspectorPanelFactory.java:40) at com.eviware.soapui.impl.coverage.panels.CoveragePanel.<init>(SourceFile:148) at com.eviware.soapui.impl.coverage.panels.EnableableCoveragePanel.<init>(SourceFile:23) at com.eviware.soapui.impl.wsdl.panels.testsuite.ProWsdlTestSuiteDesktopPanel.a(SourceFile:218) at com.eviware.soapui.impl.wsdl.panels.testsuite.ProWsdlTestSuiteDesktopPanel.addTabs(SourceFile:187) at com.eviware.soapui.impl.wsdl.panels.testsuite.WsdlTestSuiteDesktopPanel.buildTabs(WsdlTestSuiteDesktopPanel.java:218) at com.eviware.soapui.impl.wsdl.panels.testsuite.WsdlTestSuiteDesktopPanel.buildContent(WsdlTestSuiteDesktopPanel.java:121) at com.eviware.soapui.impl.wsdl.panels.testsuite.WsdlTestSuiteDesktopPanel.buildUI(WsdlTestSuiteDesktopPanel.java:114) at com.eviware.soapui.impl.wsdl.panels.testsuite.WsdlTestSuiteDesktopPanel.<init>(WsdlTestSuiteDesktopPanel.java:106) at com.eviware.soapui.impl.wsdl.panels.testsuite.ProWsdlTestSuiteDesktopPanel.<init>(SourceFile:77) at com.eviware.soapui.impl.wsdl.panels.testsuite.ProWsdlTestSuitePanelBuilder.buildDesktopPanel(SourceFile:14) at com.eviware.soapui.impl.wsdl.panels.testsuite.ProWsdlTestSuitePanelBuilder.buildDesktopPanel(SourceFile:10) at com.eviware.soapui.ui.TabbedSoapUIDesktop.showDesktopPanel(SourceFile:214) at com.eviware.soapui.support.UISupport.showDesktopPanel(UISupport.java:590) at com.eviware.soapui.support.UISupport.selectAndShow(UISupport.java:578) at com.eviware.soapui.impl.wsdl.actions.support.ShowDesktopPanelAction.perform(ShowDesktopPanelAction.java:53) at com.eviware.soapui.support.action.swing.SwingActionDelegate.actionPerformed(SwingActionDelegate.java:89) at com.eviware.soapui.support.action.swing.DefaultActionList.performDefaultAction(DefaultActionList.java:107) at com.eviware.soapui.ui.Navigator$TreeMouseListener$1.run(Navigator.java:408) at java.awt.event.InvocationEvent.dispatch(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$000(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(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) Caused by: java.lang.NullPointerException11 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.9KViews0likes4Comments