balance wrote:Can your structural testing test "anything"? What are the limits?
In general, eValid can test any web browser enabled application that runs in the IE browser (IE is the base browser upon which eValid is based).
This is a pretty strong statement, but yes, in effect, eValid can test "anything" that runs in that context. One can imagine types of applications that run in OTHER browsers that eValid can't test, but we know from practical experience that 99.99% of all web browser enabled applications will run in IE. (In fact, even if IE is not the predominant browser that it was a few years ago, all commercial enterprises as far as we know and as a matter of course make sure that their applications run OK in IE).
But, you also asked, "What are the limits?" The limitations in eValid that affect testability of web browser enabled applications are mainly in the area of media. These limitations arise because the "state" of a display -- think of a YouTube playback or a streaming video -- are not directly managed by the browser, but by some other device (codec or some similar object). Because eValid doesn't have either state information or anything like DOM access some of the best things the eValid can do just don't apply any longer.
Nevertheless, you can still measure performance and other quality factors about these "outside the eValid limits" applications using the existing eValid facilities.
eValid Support
by balance » Fri Aug 05, 2011 3:07 pm