WebLOAD User Notes

  1. WebFT is the new Agenda recording and Agenda editing tool available with WebLOAD.

Universal Agenda Authoring Tool (Universal AAT) / Agenda Authoring Tool (AAT)

  1. When recording using the Universal AAT, multipart is recorded incorrectly.
  2. Agendas created in AAT or Universal AAT should be run in the Console with the HTTP Protocol client type. To set the client type, select the Tools | Current Session Options | Client Type tab and select HTTP Protocol mode.


WebLOAD Console

  1. For optimal balancing of Virtual Client among load processes on Windows Load Machines, the spawning factor should be set to 100. The spawning factor can be set on the Tools | Global Options | Advanced tab.
  2. WebLOAD Data Drilling reports now display the page title and not the page URL. To display the URL (as in WebLOAD 5.0), the DataDrillingUrlNames flag must be set to true in the InitAgenda block:
    wlGlobals.DataDrillingUrlNames= True
  3. Incomplete user-defined transactions, due to test sessions being stopped manually, are no longer counted as failed transactions. No messages are displayed in the Log Window about aborting these transactions.
  4. Running Agendas not created in WebFT must be run in the HTTP Protocol client-type mode. To set the client type, select the Tools | Current Session Options | Client Type tab and select HTTP Protocol mode.
  5. The default HTTP version is now 1.1. To use HTTP version 1.0, select Tools | Default Options | Browser Emulation tab and select HTTP Version 1.0.

Performance Measurements Manager (PMM)

  1. WebLOAD's Performance Measurements Manager Wizard enables you to select statistics according to your application's architecture. Default statistics are available.
  2. Performance Measurements Manager measurement definitions can be saved independent of WebLOAD templates for easy re-use with other templates.
  3. WebSphere monitoring is now fully supported.
  4. If on rare occasions the WebLOAD Console crashes, and a WebSphere monitor is defined, the Java process opened by the WebSphere application client must be closed manually.

Load Generators

  1. 1 GB RAM and Pentium 4 processors are recommended for all Load Machines for improved performance and for achieving a larger load capacity.
  2. High memory utilization may occur during test sessions.

Other

  1. The following differences can be seen in the Link properties in WebLOAD 6.0 from WebLOAD 5.0.
    a. window.document.links.protocol = "http:" (v6.0), "http://" (v5.0)
    b. window.document.links.host = "led:80" (v6.0), "led" (v5.0) (#14909)
  2. The wlHttp syntax has been changed in WebLOAD 6.0 to wlBrowser. wlHttp is still supported for backwards compatibility.
  3. When gathering performance metrics from WebSphere using the Performance Measurements Manager only one WebSphere data source may be selected at a time.
  4. XML islands can be referenced using the default XMLDocument property of the XML element. wlXmlDocument is not currently supported.
  5. To run WebLOAD 6.0 with TestTalk as a service, on a machine running WebLOAD 5.0, the TestTalk service must first be disabled for WebLOAD 5.0.
  7. Running Agenda Authoring Tool (AAT) on a machine running IE 6.0 may result in unexpected behavior when working with the Table Compare and Functional Verification wizards.
  8. All WebLOAD Optimizer instructions must contain a complete URL. Optimizer instructions using a relative path for the URL are not executed.
  9. The following syntax "styleSheets", for example window.document.styleSheets should be used when referencing a style sheet.
  10. FramesCollection.length returns the number of frames in the html and does not include the html it is called from in the count.
  11. The following differences can be seen in the Form properties in WebLOAD 6.0 from WebLOAD 5.0.
  1. ThisPage=window.document.forms = http://Test/FormPage.html (v5.0)
  2. "FormPage.html" (v6.0)
  3. ThisPage[i].method !="POST" (v5.0)
  4. ThisPage[i].method !="post" (v6.0)

Previous PageNext Page