|
Background
A typical scenario we often see is that you have a script that used to
used to work and then, suddenly it ceases working.
Clearly something changed, because a newly recorded version of the
same script on the application worked OK.
So, that's a true regression and the FAILure is a valid regression
signal.
But evidently there was no visible change in the application, only some changes in the index values at which some page features were located or possibly some value in a visible text field. Re-recording the script re-established the index values and other parameters and the new script worked.
Making An Existing Script "Invulnerable"
There is usuallya way with eValid to make a script that will in the future
be insensitive to that kind of a change...so that your test will
PASS by tolerating that location change.
Here is the outline of that passage of the script.
Such a passage now will be insensitive to the particular location of that fixpoint, even when updates to the application move it around over time.
Challenge Offer
What we can offer is to provide you with one sequence like what
is described above.
Once you have one of these passages set up it is easy to do more of them because it is basically the same passage, with only the fixpoint changing.