Part 1: For you application, at least for starters, let's concentrate
on getting a fully synchronized script that does that one
test case you described: click on the GO button, wait until
the result status changes, and then click on DONE.
That variable length of time is the problematic part.
* Here is a summary of ALL of eValid's playback synchronization modes: http://www.e-Valid.com/Products/Documen ... mmary.html
The powerful part of eValid is that we can create a command that
syncs on that DOM-internal fact...
* eValid has special commands that can be used to achieve playback
synchronization based on internal properties of pages, a capability
that is essential in certain AJAX implementations: http://www.e-Valid.com/Products/Documen ... n.dom.html
Part 2: Now, use the scenario editor to create a server loading
script that names the Part 1 script...up to 10 in parallel.
Once that's done it is just Go and watch...