gasfe wrote:Does eValid's script language try to "dumb down" the real issues in testing web applications?
We don't think so.
But we will admit that there is a great deal of activity going on "behind the scenes" for each eValid command.
If by "dumb down" you mean, "provide simple commands that do complex things automatically" then, yes, eValid is guilty.
For example a simple
SyncOnText command involves running a timed loop inside the browser which scans the DOM searching for matches on the specified for a specific property to take on a specific value, all the while doing this while NOT interfering with the other activities going on in the browser in its other thereads, such as the one(s) that are running JavaScript to support AJAX.
eValid's view of the world is that to support users best the product has to take over as much of the background work as it can, so the user can concentrate on deciding such things as which text to synchronize on, not on the details of how to do it.
For just this one command in eValid there may be upwards of a thousand code lines involved in getting the required behavior. So you can see the amplification factor invovled: ~1,000:1 over writing an individual program to do the work.
If this is "dumbing down" then we accept the compliment!
eValid Architecture Support
by gasfe » Mon Mar 07, 2011 5:11 pm