eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Introduction eValid is an intuitive and powerful web solution that quickly and efficiently tests WebSites by mapping complete sites while checking page characteristics, recording and playing functional tests, doing page and site timing and tuning experiments, and imposing load on WebSites with 100% realistic behavior including built-in validation checking and performance timing. Helpful Hints This page aims to give you a Quick Start in using the eValid product. We've added helpful hints in key places on this page. When you see this image -- -- position your mouse over the symbol to get additional information.

eValid QA Suite Features General Features Site Mapping Record/Play Wizards Test Examples Advanced Load Testing

1. Launching eValid  [ Contents | Index ]

Important Note: To operate eValid flawlessly, you need the following execution environment: (1) IE 5.50 or higher; (2) Windows 2000, Windows XP, Windows Vista, or Windows 7. eValid is a full featured browser. The display looks just like a regular browser, except you'll see that there are some extra buttons. This browser is eValid, the Test Enabled Web Browser. If you are running with an EVAL or EVAUTO license key, eValid must be on the web. Regular revenue keys don't have that requirement. With an EVAL or EVAUTO key you can work on an intranet as well -- you just have to make sure eValid is connected when you launch, when you finish a recording, and when you finish a playback. Although compatible with the IE browser, you won't find every IE feature in the eValid browser. These have been taken and replaced with testing commands: Record, Playback, LoadTest, and Site Analysis. The pictures that follow show options on the eValid menu.

2. The PullDown Menus  [ Contents | Index ]

eValid tool commands are located on the eValid tool bar: Record, Playback, LoadTest, Site Analysis, Settings, Window, Help Click the pull down menus to start the main eValid functions. Actions you can take are in solid letters, for example: Record > Start Recording Conditional actions are shaded (gray); they change into solid letters when they are available for you to use. For example, you wouldn't expect to use the Record > Wizards > Link Test Wizard unless you are recording a test.

3. License Details  [ Contents | Index ]

Click Help > License Info to learn details of your license. You'll see when your key expires, whether you are using a Demo or Evaluation copy, and find our contact information.

4. Viewing Files  [ Contents | Index ]

The eValid recorded scripts and all playback results are stored in files you can look at. For example, if you're making a recording it often helps to view the script file to see exactly how eValid is interpreting your actions. Click Window > Script Window to open the dialog box that shows you your script file.

Under the Window > Logs menu you can also view the dialogs that are connected to the eValid version you are working with and as a result you can view these files only during the current session. As with any dialog box you can show any or all of them along with the eValid GUI; they will all disappear when you terminate your eValid session. Event Log: This activates an on-screen display of the current events output. Window > Logs > Event Log. A selection of main events that affect eValid operation during playback, including timing information and Messages, Warning and Errors appear in this dialog. Note that this file may be quite verbose. Message/Error Log: This activates an on-screen display of the current messages file. Window > Logs > Message/Error Log. All Messages, Warnings, and Errors appear in this dialog box. Performance Log: This activates an on-screen display of the current performance file. Window > Logs > Performance Log. Timing Log: This activates an on-screen display of the current timing file.Window > Logs > Timing Log. All outputs from the built in timer appear in this dialog. On playback the Timing Log will show actual time that correspond to all timing requests. All Above Logs: For display of all files. Window > Logs > All Above Logs

5. User Manual[Top]

eValid User's Manual is 100% online. You can bring it up using the command Help > Documentation > User Manual The User Manual has a subject search function and a complete Table Of Contents to make finding information very easy. In addition, you can access the following information: Tutorials for the complete Training Material for eValid. QuickStart for the QuickStart page for eValid. Hints for Helpful Hints on things to watch out for in using eValid. FAQs to read the complete FAQs for eValid. Incident to use the Incident Reporting Form for eValid in case you encounter any problems. License to read the eValid license agreement. eValid Home to go to the eValid Home Page.

6. Getting Help  [ Contents | Index ]

There are many other ways to get help on eValid usage, all available from the Help Menu. Click Help > About to learn about the version of eValid you are using. Click Help > License Info to learn the details of the eValid license you are using, or Help > System Information to know your operating system, IE version or Machine Host Name.

7. Site Analysis Preferences  [ Contents | Index ]

If you plan to run a site analysis -- to use eValid's unique built in WebSite search spider -- this is where you choose various preferences that control the search. You can control the depth, length, and time of the search, decide details about the search protocol, choose sites to block and sites to include, and handle every detail of your site analysis run. All searches start from the page you are on and run until the search finishes or until you interrupt it.

8. Selecting Filters[Top]

As your site map runs eValid will filter every page it visits and report to you what it finds. This menu selects the filters you want to use and programs their parameters. The filters let you look at different properties of every page visited: Broken or Unavailable Pages. If the eValid engine can't visit the link it must be broken. Pages by Download Time. Times are for full page download and rendering. Pages by Size. Size is the total byte count downloaded. Pages by Age. This finds old, large-unchanged pages. Pages by Metric Properties. Chooses pages that meet four internal metrics.

9. Choosing Site Analysis Reports  [ Contents | Index ]

At the end of the run you use this menu to decide which reports you want to view. The Complete URLs option shows the complete tree with every dependence found. The Unique URLs option shows each URL only once. You can decide if you want to see a list of URLs or the tree structure for them. And, you can choose if you want to hide references to URLs that weren't visited.

10. 3D SiteMaps  [ Contents | Index ]

Once a site map is generated you can look at a 3D-SiteMap that shows your site in full detail -- based on the data you just generated in the Site Analysis Reports. Left click or right click on the mouse to zoom in on details, or to rotate the map in any direction. The 3D-SiteMap can be annotated to change the page symbol to reflect link count, download time, page size, and many other factors.

11. Record/Play Preferences  [ Contents | Index ]

For test record and playback there are many User Preferences that affect how you make your recording, how you save the script files, and how you play back the recording. You reach the record/play preferences menu by clicking Settings > Record/Play Preferences

12. Cache Management  [ Contents | Index ]

The eValid browser gives you direct control over the browser cache. You bring up the cache manager with this command: Settings > Cache Manager The Cache Management function lets you choose between many options on how you want the internal cache handled. You can run with no cache, or with a cache that is deleted before every playback. And, you can choose to keep or delete cookies.

13. Making a Recording  [ Contents | Index ]

It's easy with eValid to record a test script. Click: Record > Start Recording. From this point on until you click: Record > Stop Recording, everything you do in the browser is saved to the script file for playback. You can set the default script file by selecting Settings > Record/Play Preferences and entering the script file name under File Management. Or you can rename the current script by selecting Save As from Window > Script Window If you are recording on a WebSite with frames you should start your recording at a page that defines the position and content of the frames.

14. Playing A Recording  [ Contents | Index ]

If you've just recorded a script file and it's still available to eValid, click File > Open Script to open a script file that you recorded earlier. Click Playback > Start Playback to start playback. Click Playback > Stop Playback when you want stop playback.

15. Using the Event Timer  [ Contents | Index ]

The timer records elapsed time in milliseconds. Click Record > Timer > Read Timer to tell eValid to read out the current time (during playback) into the Event Log or the Timing Log. You can click Record > Time > Reset Timer to set the timer to zero. Before the timer resets, eValid reads out the accumulated time up to that point.

You can create notification alarms in your script very easily. Choose Record > Timer > Set Alarm. This will open a dialog box where you can specify when you want the alarm to occur (expressed in Hours, Minutes, Seconds) and the text you want to be printed to the event log with the alarm. Once you've decided this, click Accept and the alarm will be entered into your recording script file. Click Cancel if you change your mind.

16. Editing Scripts  [ Contents | Index ]

Sometimes you may want to edit your recording. Click Window > Script Window to open the dialog box that shows the script file, then click Edit. When you've completed your editing click Save.

17. Using the Link Wizard  [ Contents | Index ]

If you have a page with a lot of links and you want to go to them all to make sure they are OK you can make a recording using the Link Wizard. Start your recording in the usual way. Then, go to a page where you want to check links. Click Record > Wizards > Link Test Wizard. eValid will insert a reference to every link on your page at that point in your script file. All such tests are delivered into the current script file. When you play back this script file you can watch the screen or read the messages in the error log to see if any links failed. For details see: Create a Link Check Test.

18. Using the Form Wizard  [ Contents | Index ]
Start your recording in the usual way. Click Record > Wizards > Form Test Wizard. eValid will automatically insert a reference to every FORM element on your page at that point in your script file.

During playback eValid will visit every FORM element, typing a default phrase into every text-entry field and clicking all of the buttons on the page.

19. Using the Button Wizard  [ Contents | Index ]
Start your recording in the usual way. Click Record > Wizards > Button Test Wizard. eValid will automatically insert a reference to every active button on your page. During playback eValid will visit every one of these active buttons and click them.

Note: The Button Wizard will "push all your buttons" but it doesn't necessarily know what they do, so you may have to edit your script file if the actions that result from "push all the buttons" don't make sense on your WebSite.

20. Recording a BenchMark Test  [ Contents | Index ]
A BenchMark Test measures the amount of time a sequence of browser action takes. The test starts the timer, browses through some pages, and then reads the timer. eValid timings of this sequence are very realistic. There is a special set of "how to" instructions to help you Create a BenchMark Test.

21. Recording an E-Commerce Test  [ Contents | Index ]
An E-Commerce test tries out an E-Commerce application by going to an E-Commerce site, selecting an object to purchase, making a purchase and taking care of the payment and confirming that the order was placed correctly. You run an E-Commerce test to confirm that your E-Commerce site is working normally, and reveal any errors along the way. There's a special set of "how to" instructions to help you Create E-Commerce Tests.

22. Recording a Security Test  [ Contents | Index ]

A Security Test tries out a login activity on a WebSite by trying both a legal login (which should PASS) and an illegal login (which should FAIL). Running a Security Test confirms that the essential protections in a login area are working correctly. To handle a secure transaction reliably you will probably want to record using Record > Security > Enter Secure Zone when you enter the secure area and record Record > Security > Exit Secure Zone when you leave the secure area. Turning the secure area processing changes the way the playback is handled so that it is compatible with secure transactions. There is a special set of "how to" instructions to help you Create a Security Test.

23. Recording a SpotCheck Test  [ Contents | Index ]
A SpotCheck Test uses the Record > Validate > Selected > Text command to make sure parts of pages don't change. This is just one kind of validation test. For details see Create a SpotCheck Test.

24. Timing Charts  [ Contents | Index ]

Every playback produces a set of logfiles that detail the results of the test. Test charts access this log data and show it graphically, as HTML documents, or in spreadsheet form. Please see the General Chart Operation, and for specifics about each chart please see the Chart Descriptions.

25. Advanced Record/Play Preferences  [ Contents | Index ]

Most websites that involve complex interactions, including those that have complex sub-windows and complex information structures, record and play with no difficulty. The recording process keeps track of the current window (i.e. the window in focus) and also keeps track of details about which frame is active. This information is put in the script file and used extensively during the test playback process. In rare cases the WebSite you're testing requires just a bit more work than simply recording what you do. Advanced Recording is a separate set of special eValid features that lets you handle Modal Dialogs, Java Applets, Javascript passages, windows that require scrolling, etc. See the menu of selections at: Settings > Record/Play Advanced Preferences A complete description of the Advanced Recording Features.

26. Java Applets  [ Contents | Index ]
Java Applets require special handling because they are not object oriented. The same applies to other kinds of "opaque" objects like Adobe Acrobat files (PDF files), and some FLASH objects. Recordings of Java Applets uses absolute X/Y coordinates and fixed image sizes, and require screen focus. You may need to use F11 to turn on Absolute Mouse Click Recording. As with all advanced recording modes the specific recording protocol depending on how the WebSite is built. Experimentation may be needed

27. Application Mode  [ Contents | Index ]
Application Mode recording is available on parent-page launched sub-windows that are not browser windows. Recording for such windows is done with absolute locations and screen sizes.

You can also use Application Mode with any type of Windows application that is present on the desk top, whether launched by your current browser page or not.

Validation modes available include checksum creation with a defined rectangle, screen capture, and validation from saved clipboard text.

28. Desktop Mode  [ Contents | Index ]
Desktop Mode recording is available as an alternative recording mode and can be used with any window on the desktop.

As with Application Mode, recording is done with absolute locations and screen sizes.

Validation modes include checksum creation with a defined rectangle, screen capture, and validation from saved clipboard text.

29. Modal Dialogs  [ Contents | Index ]
Recording of modal dialogs is done from the View Script dialog box, using a pulldown on that window. This is done because, while a modal dialog is present, there is no direct way to interact with it from the browser face.

30. Validation Functions  [ Contents | Index ]
There are several ways to validate the contents of any page on a WebSite:

Properties of the entire Document using: Record > Validate > Document > .... Properties of selected parts of the document, with: Record > Validate > Selected > .... All features of the document, using: Record > Validate > All > ... as shown in the sample below.

31. Validation Document  [ Contents | Index ]

Use the menu sequence: Record > Validate > Document > ... to validate specific properties of the page: The URL of the document. This is important if you are going to a page that redirects to a page whose URL you don't know but want to confirm. The pageTitle. Elements, i.e. the number of elements in the page. The Size of the document in bytes. The Last Modified Date of the document. The Checksum for the page. All Document Properties

32. Validate Selected Text Operation  [ Contents | Index ]

If you want to know for certain that features of a page stays the same you can Validate Selected Text on parts of your page during a recording. During a recording session use the mouse to highlight a section of the page that you want to confirm. Then click Record > Validate > Selected > Text

The image at left shows a highlighted text that has been selected by the tester and the corresponding recorded script file with the selected text recorded. The text highlighted is "dynamic testing". During playback if this text is not present in the page in the same position logically then an Error is issued. The checking is independent of the page size and type font but instead is dependent on the text being in the underlying representation at the same logical location. eValid remembers the text you highlighted and if that text has changed logical position during playback you'll get an error message. This is a very powerful feature because the script file will cause an error message if at some time in the future your page has changed in any way that invalidates the text.

33. Validate All Text In Page  [ Contents | Index ]

The Validate All Text Wizard creates a script file (i.e. a synthetic recording) that, when played back, will confirm that every segment of this page is present (independent of the HTML rendering) in the page, and will issue error reports if ANY difference is found.

34. Validate Image or Applets  [ Contents | Index ]

Lastly, you can select Record > Validate > All > Images or Record > Validate > All > Applets to record critical details of these objects. To validate images you can make a record of every image currently in the page; if any images change during playback an error message will result. When you validate applets you make a record of every applet referenced on the page and record it in such a way that if the applet is not present or changes size an error message will result. eValid's validation procedures refer to Element ID's. These numbers are generated for each element of the HTML page (text, images, applets, etc.) when the page is read into eValid. eValid uses these Element ID's to locate the exact portion of the page that you wish to be validated.

35. Principles of Load Testing  [ Contents | Index ]
eValid generates load by running multiple eValid browsers from a special LoadTest Script. You can generate a LoadTest script very easily with the command: LoadTest > New Load Test which produces the script from a table that you fill in. You can edit the script as you make changes.

36. LoadTest Script  [ Contents | Index ]

All LoadTest scripts refer to one or more regular eValid scripts. Click Window > Logs > LoadTesting Log . Normally these are scripts you have developed during your functional testing activity but they could be developed specifically for the LoadTest process. In the LoadTest script you can control the playback scripts run, how many times each is repeated, what parameters are passed to them, what slowdown ratio to use, and what User Profile to use. Because all loading is done with actual browsers, the tests can be complex, lengthy, and coherent (i.e. they can maintain state and keep track of cookies). Actual capacity in terms of number of users on one machine depends on the particular machine. Some CPU Adjustments may be necessary to maximize the number of simultaneous playbacks.

37. LoadTest Monitor  [ Contents | Index ]

Once the LoadTest test is launched, eValid will then launch additional copies of eValid each assigned to run the specified script with the specified parameters. The LoadTest Monitor shows the status of each eValid executing during the LoadTest run. At the end of the run it summarizes all of the details about each test and includes minimum, maximum, and average run times for each user. Click Window > Logs > LoadTest HTML Monitor.

38. LoadTest Chart  [ Contents | Index ]

After all of the test have completed, and all of the sub-browser that were launched by the LoadTest script have been closed, you can look at a chart that summarizes the results of the run. The chart shows, for each User Profile, the minimum, average, and maximum script playback time for all of the associated runs. Click Window > Logs > LoadTest Graph.

We hope you enjoy using eValid, the Automated Web QA Suite.