Forum Discussion

MPunsky's avatar
MPunsky
SmartBear Alumni (Retired)
12 years ago

[LoadUIWeb] Known Issues in WebLoadUI Pro 2.80

This list comprises the list of known issues in the WebLoadUI Pro 2.80 Release



The export of reports to PDF may fail if WebLoadUI is running under a user account. This happens due to certain specifics of PDF printer registration in the operating system.





  • To work around the issue, re-install WebLoadUI under the same user account with which you will export results.

     


During scenario recording Internet Explorer may crash. This can happen if you record a long scenario and the browser sends and receives large amount of data. This data are stored in the address space of Internet Explorer and potentially may cause memory overflow.





  • To avoid the problem, record shorter user scenarios and combine them into complex scenarios for test runs.

     




You may get an error message in the test log that a socket was closed and a number of subsequent error messages that requests that we not simulated. This typically indicates that during scenario recording there was a long pause between subsequent requests. Web servers close connections that are inactive for some period. For some reason, the connections were not closed during recording, but were closed during the test run. This causes the described error.





  • To work around the issue, open the problematic scenario for editing and decrease the think time for the first request that was not simulated. To do this, find the problematic request or page in the request tree, right-click it and choose Edit Parallel Requests from the context menu. This will invoke the Parallel Request Editor. Find the desired request in the editor and drag the splitter before it to change the think time.

     




Rendezvous points don't work for all the requests. To simulate realistic browser behavior during the test run, by default, WebLoadUI sends requests to the tested servers using multiple concurrent connections. If you set a rendezvous point to some internal request within a page (but not to the first request), then the synchpoint will work only for the connection, to which this request belongs. Requests of other connections will not be synchronized. This may cause incorrect simulation and may lead to invalid test results.





  • To work around the issue, put rendezvous points to the first request of a page. If needed, you can insert custom pages into your scenarios, so that the needed requests become the first requests of these pages.




WebLoadUI may hang during the test run if there is no enough space on the system drive. During the test run, the temporary log files are stored in the Temp folder (by default, it is %USERPROFILE%\AppData\Local\Temp). If the test operates with large data and works for a long time, the temporary log files may occupy several gigabytes on the disk. This causes WebLoadUI to hang and may cause overall slowdown of the system.





  • To work around the issue, it is recommended to have several gigabytes of free space on the drive, where the Temp folder resides. In most cases, this is the system drive. You may need to check the amount of free disk space on it before running the tests, and remove the unneeded files or folders from this drive. Alternatively, you can relocate the Temp folder to some other drive that has enough space.


No RepliesBe the first to reply