Following the implementation process, the testing team quickly began to experience some of the major operational benefits of TestDrive. The middle-ware upgrade project entailed almost daily builds, with parameter changes that affected several different systems. Firstly the team has to be sure that they test every component with every run, to ensure that every change and its knock-on effects were captured and verified.
TestDrive could easily cope with this, using a test bed of scripts to test every element of the public-facing web applications, picking up and highlighting any variances in the user interface. But the resultant application changes would then have to be incorporated into the new version of the script, and traditionally this would mean time-consuming and tedious script-updating.