I found a much better solution. Instead of using the Aliases name mapping you can delete that and use the Sys.Process name mapping and that way you can edit the object name mapping with a wild card.
I see what is happening, the window is being renamed window2, or window1 ect and the regional checkpoint is looking for a specific window.
What it sounds like is that your original mapping of the object contains information that varies from test run to test run. You should edit your mapping to account for dynamic property values, either by finding more static values to identify the object or using wildcards in the property values to account for the dynamic portions.
Agreed, thanks.
Exept that I can't do a wildcard with a regional checkpoitn name mapping.
Yes, you can... don't change the Regional Checkpoint, go to the NameMapping node in your project explorer, find the object you have mapped, and edit the mapping properties. Based upon your other post, you are not using distinct enough criteria to map the object.
