Forum Discussion

rwnilsen3's avatar
rwnilsen3
New Contributor
13 years ago

loadUI 1.5.0 feedback

I've just recently started using loadUI, and here is a list of things that I wish were different:

1) running a soapUI runner test using a distributed agent on Red Hat Linux is flakey. I frequently experience the case where a test will run in Local, but won't do anything when running on the agent. Then, I'll turn the agent off/on... or drag the test case off then back onto the agent... and sometimes the test will work. This is a dealbreaker for me.

2) The statistics module never shows TPS. I have no idea why or how to fix it.

3) I have a soapUI script containing 15 soap requests. Best I can tell, the soapUI runner module treats this whole script as one "request". I like it to count as 15 requests... or change the wording to be something more clear. Also, once I get statistics at the end, it's difficult to know if the response times are per soap request, or per soapUI script completion.

4) The font on the "Interval Scheduler" is so small that it's hard to tell the timescale being used. If you set duration to "30 seconds" the window looks like it says "030 min".

5) The Summary Report should show units for all numbers. It's not completely clear that all times are ms.

loadUI is a cool tool... I hope these problems have a quick solution. Be sure to focus on quality, otherwise we won't be able to rely upon loadUI.

Best regards,

Bob

6 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi Bob and thanks for the feedback!

    rwnilsen3 wrote:
    2) The statistics module never shows TPS. I have no idea why or how to fix it.

    If you mean the Statistic Component, then make sure that you have connected it correctly. To be able to show TPS, you should connect it as shown below:

    You might also have unchecked TPS by mistake in the Statistics Component's Settings. Make sure that it's checked by clicking the wrench icon in the upper right corner of the Statistics Component.

    If you mean the Statistics Workbench, which is the recommended way to view statistics in loadUI 1.5, then I need to know which component that you think is missing TPS.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    rwnilsen3 wrote:
    4) The font on the "Interval Scheduler" is so small that it's hard to tell the timescale being used. If you set duration to "30 seconds" the window looks like it says "030 min".
    That's a fair point. I'm pretty sure that it's related to a font refactoring that we made recently. Thanks for reporting this, it will be fixed in an upcoming nightly build.
  • rwnilsen3's avatar
    rwnilsen3
    New Contributor
    I went and installed loadUI 1.0.1 on both my windows XP front end machine and my red hat 5.4 agent machine.

    I created a new project, a new test case within that project, and built a simple case using a slow fixed-rate trigger and a soapUI runner.

    Within the soapUI runner I opened up the same soapUI 4.0 script that I had been using before. It would run just fine in local mode. So I tried to run it in distributed mode, and I got a much more interesting set of errors from the agent stdout (see below)

    Could it be that loadUI 1.5 was getting the same errors but failing silently? How can I check logs for both the front-end and the agent for errors?


    Error at line 1144, column 20
    org.apache.xmlbeans.XmlException: error: Unexpected character encountered while in a closing tag: '<'
    at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486)
    at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1276)
    at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1263)
    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
    at com.eviware.soapui.config.SoapuiProjectDocumentConfig$Factory.parse(Unknown Source)
    at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(SourceFile:169)
    at com.eviware.soapui.impl.wsdl.WsdlProject.<init>(WsdlProject.java:209)
    at com.eviware.soapui.impl.wsdl.WsdlProjectPro.<init>(SourceFile:132)
    at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:32)
    at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:16)
    at com.eviware.loadui.integration.SoapUIProjectLoader.tryReloadingProject(SoapUIProjectLoader.java:139)
    at com.eviware.loadui.integration.SoapUIProjectLoader.loadProject(SoapUIProjectLoader.java:115)
    at com.eviware.loadui.integration.SoapUIProjectLoader.reloadProject(SoapUIProjectLoader.java:291)
    at com.eviware.loadui.integration.SoapUIProjectLoader$FileWatcher.run(SoapUIProjectLoader.java:218)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
    Caused by: org.xml.sax.SAXParseException: Unexpected character encountered while in a closing tag: '<'
    at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
    at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)
    at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454)
    ... 15 more
    23:04:00,660 ERROR [SoapUI] An error occured [Failed to load project from file [file:/root/.loadui/fileStorage/e79a85ed9c97d410238b278fb81f9d9c]], see error log for details
    com.eviware.soapui.support.SoapUIException: Failed to load project from file [file:/root/.loadui/fileStorage/e79a85ed9c97d410238b278fb81f9d9c]
    at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(SourceFile:272)
    at com.eviware.soapui.impl.wsdl.WsdlProject.<init>(WsdlProject.java:209)
    at com.eviware.soapui.impl.wsdl.WsdlProjectPro.<init>(SourceFile:132)
    at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:32)
    at com.eviware.soapui.impl.wsdl.WsdlProjectProFactory.createNew(SourceFile:16)
    at com.eviware.loadui.integration.SoapUIProjectLoader.tryReloadingProject(SoapUIProjectLoader.java:139)
    at com.eviware.loadui.integration.SoapUIProjectLoader.loadProject(SoapUIProjectLoader.java:115)
    at com.eviware.loadui.integration.SoapUIProjectLoader.reloadProject(SoapUIProjectLoader.java:291)
    at com.eviware.loadui.integration.SoapUIProjectLoader$FileWatcher.run(SoapUIProjectLoader.java:218)
    at java.util.TimerThread.mainLoop(Unknown Source)
    at java.util.TimerThread.run(Unknown Source)
    Caused by: org.apache.xmlbeans.XmlException: error: Unexpected character encountered while in a closing tag: '<'
    at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486)
    at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1276)
    at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1263)
    at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
    at com.eviware.soapui.config.SoapuiProjectDocumentConfig$Factory.parse(Unknown Source)
    at com.eviware.soapui.impl.wsdl.WsdlProjectPro.loadProject(SourceFile:169)
    ... 10 more
    Caused by: org.xml.sax.SAXParseException: Unexpected character encountered while in a closing tag: '<'
    at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038)
    at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723)

    at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454)
    ... 15 more
    23:04:00,662 INFO [SoapUIProjectLoader] Releasing soapUI project [e79a85ed9c97d410238b278fb81f9d9c]
    23:04:03,880 INFO [ControllerImpl] Client disconnected
    23:04:03,880 INFO [ControllerImpl] Stopping scene: TestCase
    23:04:03,885 INFO [SoapUIProjectLoader] Releasing soapUI project [e79a85ed9c97d410238b278fb81f9d9c]
  • rwnilsen3's avatar
    rwnilsen3
    New Contributor
    So then I turned on DEBUG level logging in the log4j.xml file.

    I started the test... but loadUI didn't indicate that there were any "Requests" or "Running" in the soapUI runner.

    Here is the agent output I got when trying to run my awesome test remotely:

    [root@plabpt17 loadUI-Agent-1.5.0]# ./loadUI-agent.sh
    Launching loadUI Build: loadUI-Dist-2011-06-13-[3] 2011/06/13 20:56
    23:28:33,574 WARN [bayeux@15607307] setDebugEnabled not implemented
    Configuring log4j from [/opt/eviware/loadUI-Agent-1.5.0/soapui-log4j.xml]
    23:28:35,323 WARN [SoapUI] Missing folder [/opt/eviware/loadUI-Agent-1.5.0/./ext] for external libraries
    23:28:35,324 INFO [DefaultSoapUICore] Creating new settings at [/root/soapui-settings.xml]
    23:28:36,253 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [/root/.loadui/custom-soapui-scripts]
    23:28:36,746 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xop.xsd with targetNamespace http://www.w3.org/2004/08/xop/include
    23:28:37,017 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/XMLSchema.xsd with targetNamespace http://www.w3.org/2001/XMLSchema
    23:28:37,020 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xml.xsd with targetNamespace http://www.w3.org/XML/1998/namespace
    23:28:37,023 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/swaref.xsd with targetNamespace http://ws-i.org/profiles/basic/1.1/xsd
    23:28:37,025 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200505.xsd with targetNamespace http://www.w3.org/2005/05/xmlmime
    23:28:37,027 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200411.xsd with targetNamespace http://www.w3.org/2004/11/xmlmime
    23:28:37,031 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope.xsd with targetNamespace http://schemas.xmlsoap.org/soap/envelope/
    23:28:37,040 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding.xsd with targetNamespace http://schemas.xmlsoap.org/soap/encoding/
    23:28:37,043 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope12.xsd with targetNamespace http://www.w3.org/2003/05/soap-envelope
    23:28:37,052 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding12.xsd with targetNamespace http://www.w3.org/2003/05/soap-encoding
    [INFO] Started bridged http service
    -> Framework started!
    23:28:38,211 INFO [ComponentRegistryImpl] Registered Component Descriptor: soapUI Runner
    23:28:38,212 INFO [ComponentRegistryImpl] Registered Component Descriptor: soapUI MockService
    23:28:38,344 INFO [ControllerImpl] Agent started and listening on cometd!
    23:31:27,182 INFO [ControllerImpl] Client connected
    23:31:27,183 DEBUG [StreamingStatisticsAggregator] Added Endpoint: MessageEndpointImpl[connected=true,handshook=true]
    23:31:27,274 INFO [ControllerImpl] Loading SceneItem 9effaf86-5815-400f-8521-f13677437dcd
    23:31:27,276 DEBUG [ControllerImpl] REQUESTING DEFINITION: 9effaf86-5815-400f-8521-f13677437dcd from: MessageEndpointImpl[connected=true,handshook=true]
    23:31:27,816 DEBUG [ControllerImpl] Got TestCase Definition for: 9effaf86-5815-400f-8521-f13677437dcd
    23:31:28,554 DEBUG [ClassLoaderRegistry] GroovyClassLoader created: com.eviware.Statistics
    23:31:30,414 INFO [HttpClientSupport$Helper] Updating keyStore..
    23:31:30,415 INFO [HttpClientSupport$Helper] Updating keyStore..
    23:31:30,435 DEBUG [ClassLoaderRegistry] GroovyClassLoader created: com.eviware.VirtualUsers
    23:31:30,586 INFO [ControllerImpl] Started scene: TestCase
    23:31:31,201 DEBUG [ReferenceToFileConverter] getOrCreate() e79a85ed9c97d410238b278fb81f9d9c
    23:31:31,201 DEBUG [ReferenceToFileConverter] Adding e79a85ed9c97d410238b278fb81f9d9c to filesInProgress
    23:31:31,202 DEBUG [ReferenceToFileConverter] waiting for e79a85ed9c97d410238b278fb81f9d9c
    23:31:31,242 DEBUG [ReferenceToFileConverter] getOrCreate() 322f434bb9431c7c71e135e5facb9db4
    23:31:31,242 DEBUG [ReferenceToFileConverter] Adding 322f434bb9431c7c71e135e5facb9db4 to filesInProgress
    23:31:31,242 DEBUG [ReferenceToFileConverter] waiting for 322f434bb9431c7c71e135e5facb9db4
    23:31:33,253 DEBUG [ReferenceToFileConverter] File done. Removing 322f434bb9431c7c71e135e5facb9db4 from filesInProgress
    23:31:33,258 DEBUG [ReferenceToFileConverter] target is: /root/.loadui/fileStorage/322f434bb9431c7c71e135e5facb9db4 and is 20474 bytes with hash 322f434bb9431c7c71e135e5facb9db4
    23:31:33,261 INFO [DefaultSoapUICore] Importing preferences from [/root/.loadui/fileStorage/322f434bb9431c7c71e135e5facb9db4]
    23:31:33,268 INFO [DefaultSoapUICore] initialized soapui-settings from [/root/.loadui/fileStorage/322f434bb9431c7c71e135e5facb9db4]
    23:31:33,287 INFO [HttpClientSupport$Helper] Updating keyStore..
    23:31:33,288 INFO [DefaultSoapUICore] Importing preferences from [/root/.loadui/fileStorage/322f434bb9431c7c71e135e5facb9db4]
    23:31:33,303 INFO [HttpClientSupport$Helper] Updating keyStore..
    23:31:48,730 DEBUG [ControllerImpl] Got command: actionEvent
    23:31:48,732 DEBUG [ModelItemImpl] Triggering action 'RESET' on ModelItem 'SceneItemImpl[label=TestCase]'
    23:31:49,507 DEBUG [ControllerImpl] Got command: actionEvent
    23:31:49,507 DEBUG [ModelItemImpl] Triggering action 'START' on ModelItem 'SceneItemImpl[label=TestCase]'
    23:31:58,386 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854775182 dropped!
    23:32:10,341 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854774975 dropped!
    23:32:30,082 ERROR [BayeuxServiceServerEndpoint] Message with SEQ: -9223372036854774558 dropped!
    2
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Bob,

    Would it be possible for you to let us have a look at your soapUI and loadUI projects? If so, please send them to support at eviware.com with a link to this forum topic.


    Best regards

    Henrik
    loadUI team
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    rwnilsen3 wrote:
    3) I have a soapUI script containing 15 soap requests. Best I can tell, the soapUI runner module treats this whole script as one "request". I like it to count as 15 requests... or change the wording to be something more clear. Also, once I get statistics at the end, it's difficult to know if the response times are per soap request, or per soapUI script completion.

    Hmm... perhaps we could add another counter for requests made from within the soapUI TestCase. Would that make things clearer?

    Did you know that you can get individual Statistics and Terminal Output from all TestSteps by changing the value in the dropdown shown below?




    rwnilsen3 wrote:
    5) The Summary Report should show units for all numbers. It's not completely clear that all times are ms.

    I assume that you are primarily referring to the numbers in the red rectangle below? Apart from them, I think that all values have units of measurement specified where applicable.



    I just added this to our backlog of thing to fix. Thanks!

    Regards

    Henrik
    loadUI team