NigelOldfield
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Enhance the Conditional Goto Test Step functionality
The Conditional Goto Test Step functionality is quite restrictive compared with equivalent SoapUI Test Steps such as Property Transfer. This limits how useful the Conditional Goto is and therefore how powerful SoapUI scripts can be without resorting to Groovy. I am not sure how to configure the existing Conditional Goto for response messages containing CDATA, so for us the Conditional Goto is never used. In my opinion, using Groovy, for a tester without a development background, can be a significant hurdle to overcome. Please enhance the Conditional Goto functionality to allow source data other than just the previous response message. I suggest a user interface similar to the Property Transfer to allow any message or property to be selected for comparison. Property Transfer (flexible): Conditional Goto (very limited): Thanks.Re: Is anyone else having problems moving TestCases within a TestSuite?
Hi Tanya Gorbunova, Thank you for checking and apologies for not researching the issue more before posting my comment. I have now checked further by repeatedly binary chopping the content of my Ready!API 1.3.1 Project file. It looks like the significant factor between success and failure of a Test Suite move is the existance or otherwise of a SecurityTest created via the Secure option. ThanksRe: Is anyone else having problems moving TestCases within a TestSuite?
TestCases moves within a TestSuite using Ctrl+arrow key seem to be working for me, but trying to move a TestSuite within a Project causes serious damage to my Ready!API 1.3.1 necessitating exit (no changes saved) and restart. Any workarounds welcome!Re: Difficulty making use of LoadUI NG
I think I have identified the cause of my LoadUI NG problem. It is a combination of CDATA and Contains Asertions. It looks like, internally, SoapUI checks against the response message containing a CDATA section but LoadUI checks against a version of the response encoded with < and > instead of CDATA. For example, the following Contains Assertion passes in SoapUI NG but FAILS in LoadUI NG (when the text is embedded in a CDATA section): <txDescription>Accepted</txDescription> Whereas the following passes for both SoapUI NG and LoadUI NG, with "Use token as regular Expresion" ticked: (<txDescription>Accepted</txDescription>)|(<txDescription>Accepted</txDescription>)Please consider reintroducing the Total Runs option to LoadUI NG
Prior to LoadUI NG I made use of the Total Runs option of the SoapUI load testing functionality to provide baseline transaction turnaround timings. I don't think the current LoadUI NG options can give me the same level of control. Please consider reintroducing the Total Runs option to LoadUI NG. Thanks.Property Transfer order is lost
To note a possible Property Transfer issue - I think the order of individual transfers within a Property Transfer SoapUI TestStep, explicitly set via the move up option, can get lost following Ready!API (1.3.0) restart. Two interdependent property transfers were created in one property transfer test step but in the wrong order (the dependency was in order to extract an xml node value from within a CDATA node). The order was corrected using the reorder options within the propertry transfer window (via “^”). The test step sequence of Soap request 1, property transfers, soap request 2 was tested and worked. Next time Ready! API was started up, however, soap request2 failed because the order of property transfers had reverted to the original, incorrect order resulting in an old value being used in soap request2. Workaround: I resolved the problem by copying the first transfer and deleting the original, but there may be a minor defect in SoapUI NG.Difficulty making use of LoadUI NG
It looks like LoadUI NG is telling me my load test is failing but I cannot see how to investigate the problem. It reports 100.00 Fail% and does not trigger two of the three test steps (see screenshot). I have a simple Test Case of three steps, two SOAP requests with a Property Transfer between the two requests. This TestCase runs successfully in SoapUI NG. I asked Ready!API to create the corresponding LoadUITest for the TestCase and then ran it, it failed, where do I go from here? Previously I made use of SoapUI PRO load tests but so far I have not managed to get any value out of LoadUI NG. I suspect I just need to know where to look for information, both user guide and test diagnostic information, any help welcome. Since starting this forum question I have tested another variant and observed the following on the Ready!API log tab, can I have help interpreting this information? Tue Jun 09 12:03:54 BST 2015:ERROR:Failed to publish message. java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at net.engio.mbassy.dispatch.ReflectiveHandlerInvocation.invokeHandler(ReflectiveHandlerInvocation.java:23) at net.engio.mbassy.dispatch.ReflectiveHandlerInvocation.invoke(ReflectiveHandlerInvocation.java:49) at net.engio.mbassy.dispatch.MessageDispatcher.dispatch(MessageDispatcher.java:30) at net.engio.mbassy.subscription.Subscription.publish(Subscription.java:73) at net.engio.mbassy.bus.MessagePublication.execute(MessagePublication.java:43) at net.engio.mbassy.bus.AbstractSyncAsyncMessageBus$1.run(AbstractSyncAsyncMessageBus.java:55) at java.lang.Thread.run(Unknown Source) Caused by: groovy.lang.MissingPropertyException: No such property: scenario for class: com.eviware.loadui.api.events.notify.scenario.LoadUIScenarioUpdateNotification Possible solutions: scenarioId at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:51) at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:63) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:293) at com.smartbear.loadui.view.inspectors.ScenarioInspector.onLoadScenarioUpdateNotification(ScenarioInspector.groovy:119) ... 11 more Thanks,
