The basic sequence you have outlined ought to be no problem. It's good!
We're assuming that you want to measure the end-user performance of a web-based email system. Let us know if you mean to test a non-web-based system, which also is possible, but would be using Application Mode rather than Browser Mode.
There's a worked example that illustrates how DOM-processing commands process a Gmail account.
Here is an example of AJAX usage that shows how eValid's IndexMotion commands are used to test the Google Gmail application (which is notoriously difficult to test):
http://www.e-valid.com/Products/Documen ... ple02.htmlProbably the only thing you need to do is add some ResetTimer and ElapsedTime commands to the script.
* Here is how to use the eValid internal timer facility to measure how long one or a set of commands takes, as described here:
http://www.e-Valid.com/Products/Documen ... tml#timing* These commands are available from the eValid GUI as described here:
http://www.e-Valid.com/Products/Documen ... html#timerOr, you could use the SaveRecord command to create local file with detailed timing data:
* Here are the detailed instructions for use of the SaveRecord command, which outputs in-progress test data to an external file:
http://www.e-Valid.com/Products/Documen ... ecord.htmlLet us know if this helps out!