You're right...if your UI is changing then the straightforward method of recording user actions in the browser and playing them back won't be reliable. Even the powerful
Adaptive Playback feature of eValid won't overcome changes reliably enough.
The solution is to create a script -- which we recommend be based on use of what is originally recorded by the eValid recording engine -- and make it a "structural script" that relies on logical positions in the web page that do NOT move around as the page changes.
Here is a page that will serve to show you how to do this by example:
Testing With DOM Interactions -- Guide to Examples. The hardest part is to find the "fixed point" about which to pivot the test actions, but this turns out to be easy enough if you study your page a bit.
eValid Support