Forum Discussion
Yes, that is almost definitely the problem. In your NameMapping, there are most likely properties whose values change each time you build the installer. I'm guessing that at least a portion of those properties is still static. You can edit the property values to then use the * wildcard to replace the dynamic portion of the value.
Another possible problem is timing. Keep in mind that test automation runs as fast as possible. So, as soon as it clicks on something, it tries to go on to the next step. If there are places where there needs to be a delay in order to wait for an object to appear on screen or something else to complete a process, these need to be added after the fact. WaitChild, WaitAliasChild, WaitProperty, etc... all these methods are specifically in place in order to allow a "smart" waiting for an object or propertiy to resolve before the test continues.
Related Content
- 4 years agoJackalNZZ