It looks like E-Test retains the actions that led to a page being displayed on the page, rather than recording actions on the page before its submitted.
It seems that this would limit the use of this script in a job.
Is there any way I can parameterise the actions themselves (and not parameterize the action parameteres, which seems easy enough)
// The Persistent Bugger
Man good question...I thought I was the only one confused by this. Took me awhile to realize what each page of a script was actually referring to for naming purposes.
Because of this I have avoided Jobs up to this point because I have been so unsuccessful at gettings scripts to run back to back to perform a suite of tests so to speak.
2) Do something
Second script wont run because its lost. However if I record the EXACT same stuff from 1 and 2 into on script it works fine.