Forum Discussion

NigelOldfield's avatar
NigelOldfield
Occasional Contributor
11 years ago

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.

 

LoadUI NG unexplained failure.PNG

 

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,

 

1 Reply

  • NigelOldfield's avatar
    NigelOldfield
    Occasional Contributor
    10 years ago

    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>)|(&lt;txDescription&gt;Accepted&lt;/txDescription&gt;)