Your TAS has been running successfully on a Windows/GUI based SUT for some years. The SUT has undergone minimal change over the years to maintain business as usual, deploying six-monthly releases for minor enhancements and bug fixes using a waterfall lifecycle.

The TAS has not changed at all during this period. The current project for the SUT will be using the Scrum methodology to deliver a more modern, competitive, user interface. It is in the release planning stage with an agreed release backlog and set of sprints outlined.

The move from lengthy waterfall releases to shorter sprints has led you to conduct a review of the current TAS to make sure it is robust and fully optimised for the timescale challenges of the new project.

What two steps would be BEST to undertake during the review?

a) Ensure that new automation code is using the same naming conventions as existing code. b) Perform a full regression run in Sprint 1 to identify what improvements could be made to the TAS for future sprints. c) Ensure that the TAS is using the latest libraries for the operating system. d) Review the functions that act upon the controls for the GUI for possible consolidation. e) Involve the test team to see what ease-of-use improvements they would like to see made to the TAS.