After using the latest Rational Robot, it seems that record and playback testing is possible. I have not used any other automated testing software, but after reading the Software Test Automation by Fewster/Graham, I felt that all tests needed to be scripted from scratch, due to the problems of GUI change etc. However the Robot tool links to the objects rather than GUI position. This seems to overcome one of the major hurdles the record and playback tools.
Also, it has the capability of adding in data verification throughout the script, and it also has a data dictionary function which can be linked in to a spreadsheet etc. I believe comments can be added in to the script as well.
With these facilities, do scripts really need to be built up from scratch, simply be recorded and run? I have not read anything that gives other advantages of pure scripting over the record/playback method.
Look forward to your replies.
We use Record and Playback extensively and currently have 3,000+ scripts in 14 projects. Four of these projects are in the 300MB size area so they are not small projects.
Unless your AUT changes radically from release to release the maintenance is usually minimal. But, you should use good structured programming by making as many of your scripts as possible generic and reusable. This will reduce maintenance even further. You are correct that in identifing by object name is essential but you can also work with objects identified by text. This is a brief answer so if you have more questions send them out.
DC Interact Commerce Corporation