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

This table compares how well various technical methods can test website activity from four alternative perspectives:

• eValid InBrowser Technology. All testing funcionality is achieved entirely within a fully functioning browser. (Technology Diagram)
• HTTP Protocol Emulation. This method simulates HTTP protocol activities independent of a browser. This method accesses all activity on the HTTP from multiple browsers. (Technology Diagram)
• Browser Proxy Based. This method wraps a browser in a proxy and achieves testing by capturing and replaying activity to/from the browser. This method accesses only the activity to/from each wrapped browsers. (Technology Diagram)
• Windows Desktop Based. This is the method used by most client/server based test systems. It involves activity capture/replay within the main Windows event loop.

See the Comparative WebSite Testing Technology Levels and the summary of eValid Advantages.

Issue Description [Requirement]	eValid InBrowser Technology	Windows Desktop Based	HTTP/S Protocol Emulation	Browser Proxy Based
Functional Testing Capabilities
Handle basic website navigation (record and play URL sequence).	Yes	Yes	Yes	Yes
Handle HTML FORMs.	Yes	Yes	Partial	Partial
Adapt playback to moved URL link with same visible text.	Yes Adaptive Playback	No	No	No
Handle JavaScript.	Yes	Partial	Navigation events only	Navigation events only
Handle Java applet clicks, type-ins.	Yes	Yes	No	No
Handles HTTP/S.	Yes	Yes	Possible	Yes
Provide for multiple session IDs.	Yes	Partial	Requires programming	May require programming
Handle FLASH objects.	Yes	No	No	No
Handle modal dialog type-ins, clicks, other user interactions.	Yes	Partial	No	No
Record non-browser objects interactions (e.g. Adobe Acrobat Reader).	Yes	Yes	No	No
Record and play relative or absolute mouse and keyboard activity that preserves browser state.	Yes	Depends on WebSite implementation	No	No
Handle DHTML.	Yes	Limited	Requires programming	Requires programming
Handle parent/child windows that communicate.	Yes	Yes	Very difficult	Very difficult
Validation Modes
Documentation validation (size, last modified date, element count).	Yes	Partial	Possible with programming	Difficult with programming
Validate page text fragment(s) independent of rendering.	Yes	Difficult	Difficult	Difficult
Validate image sizes.	Yes	No	No	No
Validate partial image (selected screen rectangle).	Yes	Partial	No	No
Validate page text fragment(s) independent of rendering.	Yes	No	No	No
Synchronize & validate playback on text string match.	Yes	No	Difficult	Difficult
Synchronize & validate playback on selected screen rectangle.	Yes	No	No	No
WebSite Timing, Page Tuning, Monitoring
Time entire test session, set alarms.	Yes	Partial	Limited, requires HTML analysis program	Limited, requires HTML analysis program
Obtain detailed download timings of page elements.	Yes	No	Requires programming	Possible with programming
Alarm & monitoring features built in.	Yes	No	No	No
Server Loading
Selectable page serve modes (FULL, TEXT, URL).	Yes	Difficult	Only URL	Only URL
Playback with adjustable wait times (think times).	Yes	Difficult	Difficult	Difficult
Modem speed simulation.	Yes	No	Difficult	Difficult
Parallel playbacks (multiple browsers), same session.	Yes	No	No	No
Parallel playbacks (multiple browsers), multiple sessions.	Yes	No	No	No
Synchronized focus among competing parallel browsers.	Yes	No	No	No
WebSite Analysis
Measure slowest loading pages (user specified time) on sub-website.	Yes	Timing will be difficult	Very difficult	Very difficult
Measure largest pages (user specified time) on sub-website.	Yes	No	Very difficult	Requires programming
Enumerate client-side broken links on sub-website.	Yes	Only with manual operation	No	Very difficult
Enumerate non sub-website pages.	Yes	No	Very difficult	Very difficult
Search all sub-website pages for string match.	Yes	No	Very difficult	Very difficult