Increase timeout for mapped object with extended find
Hi
In our project we have a very large namemapping tree. As the application under test is expected to change during the release-cycle, I have mapped many of the objects using Extended Find, and then moving the objects as far up the tree as possible. This worked great, the namemapping became more robust to changes. But now our testers are reporting the following error is appearing:
Searching for the mapped object "btnFeedbackTestStartRight" took a long time. This happened because the sought-for object has the Extended Find attribute enabled, and the test engine searched for this object on all levels down the object hierarchy.
To speed up the search and improve the test performance, add more parent objects of this object to the Mapped Objects tree of Name Mapping.
I cannot easily add more parents to the allready mapped objects, but in the future I can of course try not to move objects as far up the tree as I have done previously. But right now I need a work-a-round to get this error message to disappear. Is there someway to increase the timeout for searching the namemapping tree without hurting other parts of the test performance?
We are using TestComplete 9.20.2460.7.
Best regards
Lars Lund Olsen
In our project we have a very large namemapping tree. As the application under test is expected to change during the release-cycle, I have mapped many of the objects using Extended Find, and then moving the objects as far up the tree as possible. This worked great, the namemapping became more robust to changes. But now our testers are reporting the following error is appearing:
Searching for the mapped object "btnFeedbackTestStartRight" took a long time. This happened because the sought-for object has the Extended Find attribute enabled, and the test engine searched for this object on all levels down the object hierarchy.
To speed up the search and improve the test performance, add more parent objects of this object to the Mapped Objects tree of Name Mapping.
I cannot easily add more parents to the allready mapped objects, but in the future I can of course try not to move objects as far up the tree as I have done previously. But right now I need a work-a-round to get this error message to disappear. Is there someway to increase the timeout for searching the namemapping tree without hurting other parts of the test performance?
We are using TestComplete 9.20.2460.7.
Best regards
Lars Lund Olsen
