Benchmark and Java Applet Test Scenario

1. Benchmark and Java Applet Test Scenario Presentation Outline Introduction to Benchmark Testing Procedure to create the test Benchmark Playback Results of the Benchmark testing execution / playback The Actual Recording Process Introduction to Java Applet or ActiveX Control Testing Procedures to create the test Settings needed Results of Playback of ActiveX Control Test

2. Introduction to Benchmark Testing • The Benchmark Test measures the amount of time a sequence of browser actions take. • The test starts the timer, browses to a number of pages, and then reads the timer. • Because eValid runs from a browser -- viewing the pages like most web users do -- the times measured are realistic. • Measures the performance.

3. Procedure to create the test • Record from eValid browser from Window > Script Window • Recording can be seen as creating at the same time • Browse through a few URLs randomly from Record > Start Recording. Click any link on the selected page, or type in a new URL • Continue navigating to new windows • Stop the recording

4. Benchmark Playback • To benchmark the site recorded in the script, play back the Benchmark Script File several times. • This will make sure the results of a Benchmark Test are meaningful. • To enable the Multiple Playback option, begin by clicking Settings > Record/Play Preferences to enter the Preferences Window. • Enter the amount of times you would like to run the playback in the Multiple Playbacks 'n' value box and make sure Append to Logs is checked. • Click on Playback > Control Playback > Run Multiple to playback your recorded script 'n' times as set previously in the Multiple Playbacks 'n' Value box.

5. Results of the Benchmark testing execution / playback • Playback results from the timing log and history function • See which run generate the slowest and which one generate the fastest • eValid Dynamic Analysis Charts and Descriptions displays the total elapsed times of multiple playbacks • When the multiple playbacks have completed, open the Timing Log by clicking Window > Logs > Timing Log • Timing Log tells no. of URLs visited, no. of URL page element, downloading time and total time

6. Results of the Benchmark testing execution / playback • The History Chart, derived from the Timing Log, compares the total running times of all playbacks appended in the log file • In the History Chart -Green is used for events that ran to COMPLETION -Red indicates an event on which an ERROR message was issued -Yellow implies an event that generated ALERT message of some kind

7. The Actual Recording Process: • Initial Link http://www.msn.com/ • Type in Link http://www.sjsu.edu/ • Click to http://www.sjsu.edu/welcome.html • Click to http://search.sjsu.edu/ • Go Back To http://www.sjsu.edu/welcome.html • Type in Link http://www.engr.sjsu.edu/ • End recording

8. Introduction to Java Applet or ActiveX Control Testing • Demonstrates capabilities of eValid in manipulating ActiveX, i.e. to demonstrate eValid's ability to record, test and playback embedded on web pages that utilize ActiveX Controls. • In this Scenario, the element is static, means they are not changing constantly basically simple button “pressing” scenario. • Confirms Active X Support, i.e. it confirms if such are functional by keyboard and mouse movements and clicks.

9. Procedures to create the test • Start the test by going to the Web page with the Java Applet. • Settings > Record/Play Advanced Preferences > Applet Recording (Any actions perform in Java Applet will be recorded in the script file.) • Navigate through the page using the Applet. • Record > Stop Recording. Stop Recording

10. Settings needed

11. Results of Playback of ActiveX Control Test • Playback results from the timing log • Timing Log tells no. of URLs visited, no. of URL page element, downloading time and total time