hxing wrote:You keep pointing out how "complex" eValid is "under the hood", but can you explain what makes it so complicated? It seems so simple!
Many users are quite mystified about how eValid obtains such reliable results, while appearing to be so simple on the surface.
The answer is that, internally, eValid is a full browser and the user/test has, through the script/command language, full access to
everything that is available programmatically to the browser
per se. Inside, there is a LOT of functionality available. What eValid does is interpret each command with a specific internal code sequence that uses these resources to produce the right effect.
In other words, eValid -- by design -- hides that detail from you so you can concentrate on getting the job done, not on learning how to program a browser. The user benefits...a clean, simple product with an easy to use interface, that reliably handles 99.99% of the tasks needed in QA/Testing/Performance Tuning work.
eValid Support
by hxing » Mon Mar 21, 2011 2:48 pm