clumisy wrote:Are there any kinds of web applications that eValid cannot test?
Indeed, every technology has limitations, but before identifying what we think some of the problem areas are it is important to emphasize that, as far as we can determine, eValid can test the functionality of essentially ALL web applications.
Some of the problem areas we often encounter include: (1) testing a video or a movie, because there's no precise way to identify a "frame" in the move (digital transmission of videos is not like a 30 frame/second film projection); (2) pages which have dynamic content, because if the structure of the page changes while you are running a test on it, it's impossible to know what's where, so a static test script won't ever work; and (3) testing a "broken" page, where the HTML is so messed up that the DOM for it is impossible to decode (even though, due to the tolerance of modern browsers, the page renders OK).
The point of the above is that these are "six sigma" type problems. So, eValid therefore handles everything out through "five sigma" (five standard deviations).
eValid Support
by clumisy » Tue Aug 16, 2011 4:57 pm