Why don\'t you use object maps?
I have noticed in several posts that many people do not use object maps. Instead, they Find() all objects. I am curious why you don't use the object map.
I have always believed the toughest part of automated testing is determining the best way to reliably maintain references to the objects/fields within an application. You need to be able to update theses references when something changes in your application and do it quickly and effeciently.
I have used Rational Robot for years to test a Client/server application and we maintain external files that contain the recognition method for each field in our application. If the recognition method for a field changes, we update the single external file and it fixes all scripts that use that field.
I am now going to start testing a Web application and I was debating using RFT mainly because I like how it creates the object map. The object map seems to do everything for me that I used to maintain in external files. Also, the object map uses multiple properties to identify the field which helps keep you scripts running even if something slightly changes.
So why don't you use object maps?
Re: Why don\'t you use object maps?
It depends purely on the requirement and also if your application changes a lot ( like controls move around and the parent-child hierarchy changes ), then dynamic Find is very useful.