• Device Simulation: Using the eValid SetUserAgent command to set the User Agent String (UAS) so that the subsequent browser activity is reported to the server as if it was being requested from the specified device. eValid does this without needing the actual hardware and software! The server responses to client-side user requests made in this way behave as if it was talking to the mobile device.

• Content Validation: Once a script is running, you need to validate that the eValid rendered output matches what you expect in the actual device. Here is a Rendering Comparison for Common Devices Vs. Device Emulator. As you can see, other than the screen size, the rendering by eValid is identical to that for the mobile device. This confirms that evalid is rendering your mobile application correctly.

• Functional Testing: To illustrate how this works we ran an experiment that applied a simple test to 100 Mobile Devices, and recorded download sizes and times for each cases. A sample of that data is shown here, with some Selected Screenshots of how the server content varied as a function of the different devices and software versions simulated (with download byte counts for each device shown).

  The most interesting thing we saw was that the asymmetric ratio of Download Bytes vs. Download Time, which illustrates that some servers are not prepared to deliver mobile content to every kind of device.

• Server Loading: Functional tests lift easily to a server loading context, with multiple eValid instances (we call them Browser Users or BUs) working in parallel to create the load. This is illustrated in the experiment that we ran to drive a mobile application from a simulated smartphone up to 1,000 BUs -- up to 1,000 simulated users. The resulting Chart of Derived Internal Response Times shows that this particular server began to have a problem beyond ~200 simultaneous users.

The thing to remember is that eValid can effectively drive mobile devices that support web applications perfectly well, and can impose realistic load levels sufficient to identify bottlenecks.

• Is eValid available on a "software as a service" basis? -- Discussion of available licensing options.
• eValid Is Patented -- Details of how the end user license agreement works.
• Does eValid work with IE 9? -- Formal confirmation of IE 9 operation.
• How does duty cycle come into play in server loading work? -- How to use low duty cycles to amplify loading levels.
• Structural Testing Commands -- Access to examples of DOM manipulation script sequences.
• I want to know Automatic Page-Waiting Algorithm -- Details of eValid's internal page synchronization logic.
• Can eValid create a non-visible-text validation from the GUI -- How to "validate anything" on the page with DOM access commands.
• Is the browser overloaded due to structural commands? -- Details about manual/structural commands and synchronization.
• Limited on the number of BUs -- Tradeoffs on capacity vs. machine power.
• How do you compare eValid with eggplant? -- Alternative technologies described.

Feel free to Ask Us for additional information about these topics.

This webinar discusses eValid's architecture, how to organize functional tests of a mobile web application, how to apply these tests to a server when disguising eValid as any mobile device, and how to collect and interpret critical performance data.

Business White Paper: Automated Testing of Modern Web Applications

• How Web 2.0 and AJAX stress test tools are making testing more difficult.
• Why assuring the quality, reliability, and performance of critical "front end" applications is critical.
• What market and technical forces led to the creation of eValid's technology.
• How eValid can help non-technical or novice testers in test creation.
• How evalid's approach makes scripting much faster and reduces overall test cycle costs.

Click here to request a copy of this Business White Paper: Download Request.

• Check out the eValid Frequently Asked Questions (FAQs).
• Watch our revised Annotated/Animated Movies to see how eValid works from the GUI level, and learn how eValid treats specific testing areas.
• If you run into a tricky problem testing a website, you might consider checking out the 40+ entries in our Worked Solutions Resource. You'll find a wide range of already-worked examples showing how eValid solves typical testing situations.
• For general eValid usage you may wish to check into the set of our "top 99" Power User Tips & Tricks. They cover everything from simple functional testing to detailed LoadTest experiment development.