Hi Robert!
I know about this feature, but it does not work for me. Don't know why.
Right now I have created a simple test, which should type few symbols into the some Editor.
I unchecked "Show Ambiguous Recognition Warning" item for the mapped element (wndTkTopLevel), then ran the test and received again this warning to the log:
Hi!
Please try this
1. Disable in NameMapping - the option "Extended Find" on the object (in 'Mapping object' panel)
2. Before start test - for the TestComplete window to set the smallest size
3. During test, try set focus on the parent object or on the web page.
Is it work?
pyatakov wrote:
3. During test, try set focus on the parent object or on the web page.
Can you explain in details what did you mean?
baxatob wrote:
pyatakov wrote:
3. During test, try set focus on the parent object or on the web page.
Can you explain in details what did you mean?
This mean that when you see some object on form even with a flashing carriage it does not mean you can do some action with this object at once, you MUST set focus on this object
F.e. when you see some edit on form, before, you can write some text in edit, you MUST CLICK left mouse button on edit and THAN you can write some text in edit
Hi,
Good to hear that the sequence you've mentioned have helped in your case.
However I think that this is something specific to either your namemapping or your tested web application as personally I never met with the requirement to set focus to the control before it is possible to interact with it after it was found either as an aliased control or as a result of some of the FindXXX() functions.
Yes, sometimes setting focus to control is a good practice to move it into view when TestComplete cannot do this itself. But in all cases this was due to web application's design and not in any way a requirement to be able to interact with the control.
