Your e-Business Quality Partner eValid™ -- The Web Quality Suite
Browser-Based Client-Side Functional Testing and Validation Page Timing/Tuning Transaction Monitoring. WebSite Spidering & Analysis and Realistic Server Loading.
© Copyright 2011 by Software Research, Inc.

eValid -- AJAX Performance/Load Testing: Questions Asked
eValid Home

Summary
A number of questions were raised in the 27 January 2010 webinar, and we have answered all of them in the eValid User Forum. The answers are in the approximate order in which they were asked during the webinar.

  1. Recording the mouse position -- About recording of mouse clicks: brower context or desktop face?

  2. Screen comparison test check -- Advantages and limits of the screen synchronization method.

  3. The eValid PageMap... -- About the capabilities of the eValid PageMap tool to study DOM values.

  4. How many concurrent scripts can I run? -- Methods to run 100's or 1,000's of browser users (BUs) in server loading projects.

  5. Load test a shopping site -- How to handle a typical shopping site in load test mode, parametrically.

  6. The nature of a dynamic page -- How eValid handles testing of DHTML pages.

  7. Can I test some safety property? -- How to handle "safety properties" that are set internal to a web page.

  8. "Application mode" recording -- Can eValid also record activities in opaque web objects?

  9. The user agent string -- Using the eValid agent-string manipulation capability to simulate other browsers.

  10. A Script Command -- Can eValid forcibly manipulate network packets?

  11. Synchronize the BUs -- Synchronization between independent BUs.

  12. Is there any cross-machine sync capability? -- How to coordinate BUs across machine boundaries.

  13. Is there a branching/IF capability in the scripting? -- The conditional control statements in eValid are called "flags".

  14. Data input file -- How to use the eV.Generate subsystem to generate random values.

  15. The playback speed -- Variable and/or random values for the playback speed (wait times).

  16. A DOM index/element number -- How evalid records, and uses, page-internal DOM source index numbers.

  17. An incorrect input value -- Validating correct processing of an input error?

  18. The wait commands -- How the wait commands affect playback reliability: what fails if they are eliminated.