My application has evolved, many buttons and images which I used to interact with no longer exist.

The Visual Tests which interacted with these objects have now been removed as the tests are no longer relevant.
My customer has the following issue:-

New object map entries have now been created for the evolved application, to replace the buttons and images which no longer exist in my application.

There are now many obsolete entries in the object map which I no longer require.

The existing “Purge Asset Version” feature is not suited to my scenario as I have a single object map for my project.

I would like an additional method to be introduced to the “Purge Asset Version” feature whereby object map entries which are not used in any existing Visual Tests for a project are removed.

The introduction of this feature would decrease the size of my object map as well as the size of the database significantly.

Many man hours would be needed to manually perform the requested feature as each screen of the application would need to be tested and cross referenced for every single object map entry to determine if the object can be deleted. The object map has hundreds of entries.

Most of our automation scripts are created as Visual Tests; and for a number of reasons do not like to use Application Configurations and Object Maps in our projects.

With this type of approach however; it is difficult to create the type of decision logic that we need, because we cannot enter full XPath queries in the Value field of the condition designer.

For example; if I wanted to test that a dialog button exists on screen, and run a child test if this returns True; I would like to enter the following Xpath for Value1 in the Condition Designer:

"//Dialog//PushButton[@caption='Ok']".Visible

During playback no errors will be reported; but the child test that should run when this is visible; is skipped even though the control is visible.

This works when using Application Configurations and searching for a window within the referenced app; and also if you enter the Object Map for the dialog button in Value1 of the Condition designer.

But when no App Configs are present, it seems the condition is not evaluated properly, and may be being treated as a literal string rather than an XPath locator.

The Visual Test framework would be significantly more flexible; were it possible to enter any Xpath string in the condition or expression designer, and can search the entire Desktop for the matching control (as can be done via the Find method in .Net scripts).

We use a similar approach through a .Net script as a workaround; so a boolean indicating whether or not the control is visible; is passed back to the calling Visual Test, and then used in the Condition Designer.

It would be nice to have this option; which is provided in other functional testing tools such as QTP.

My application has evolved, many buttons and images which I used to interact with no longer exist.

The Visual Tests which interacted with these objects have now been removed as the tests are no longer relevant.
My customer has the following issue:-

New object map entries have now been created for the evolved application, to replace the buttons and images which no longer exist in my application.

There are now many obsolete entries in the object map which I no longer require.

The existing “Purge Asset Version” feature is not suited to my scenario as I have a single object map for my project.

I would like an additional method to be introduced to the “Purge Asset Version” feature whereby object map entries which are not used in any existing Visual Tests for a project are removed.

The introduction of this feature would decrease the size of my object map as well as the size of the database significantly.

Many man hours would be needed to manually perform the requested feature as each screen of the application would need to be tested and cross referenced for every single object map entry to determine if the object can be deleted.

The object map has hundreds of entries.