This chapter has dealt with issues related to constructing and locating UI elements constituting the automated tests. Firstly, we saw how elements are on one hand added automatically by Test Studio and on the other hand added manually with custom-friendly names. Secondly, the mechanism by which Test Studio forms the Element repository at startup was explained and demonstrated by tackling those element's properties. Thirdly, the element's find expressions were described while also exhibiting the options available to constructing filter expressions based on the controls' properties. Finally, the last section dealt with a way to provide a flexible, centralized, and maintainable element repository by saving the element's Find logic in a unified physical file.

By that we would have tackled from different sides, the element recognition and reliability problem raised at the beginning of the chapter. The material in this chapter wraps up the learning of functional automated testing started in the first chapter and continued in the second. Next, we will see how to create manual test scripts inside Test Studio and automate their execution process.