To answer your first question, I'd suggest reading the articles concerning waiting for objects, properties, and so on found at this link. Basically, what you're going to want to do is insert some logic utilizing one of these wait methods into your test. That way, before you go to try and click on the dynamic button, you first check to see if it exists using one of the Wait methods.
As for documentation, I know there are some third-party books and such out there. I'm sure someone will pipe up with it. But, honestly, that's what we're here for. You got questions? We got answers. ;)
I would like to add more information on the first question because I still need help.
The problem is that as soon that I enter a text in the textbox, it appear an autocompletion list witch I can select a choice that is display Under the textbox itself. It is that event of the autocompletion list that TestComplete seems to not recognize. As long as I do not make appear that list manually Under the textbox, TestComplete is not capable to reconize the object. It seems to be invisible for TestComplete on a playback. Could you help me to reproduce that event in a keyword test or a script.
Regards,
Nathalie
From your original question, you recorded the steps initially. Could you paste a screenshot of the keyword test or the script you recorded? Usually, the recording will expose how you need to reference that auto-completion so you can code around it.
I join you my Key word test "AssignationEssais"
the Keyword test stop at the "textnodeTestComplete" item and launch an error
thank you for help
OK, that's excellent.
So, basically, what is probably happening (and this is conjecture based upon experience) is that there is a slight timing delay between when your keyword test enters the text and when the text box pops up. However, during that delay, your test is continuing and is attempting to click on the text box before it exists or before it has fully populated. That is what is causing your general problem... that the "Click" is being attempted before the text box is fully rendered.
Three ways you can solve this:
1) Insert a Delay between when you type the text and when you click on the text box. This is the quick and dirty way of doing it. It works but it's clumsy in that you are hardcoding the delay. What if you run the test on a machine that performs more slowly? Is your delay going to be long enough. It works, but, as I said, it has it's problems.
2) Use the custom timeout option to specify to wait some time for the object to be present before attempting the click. Information on this can be found at https://support.smartbear.com/viewarticle/73343/. I've had some luck with this in the past but I've found that, along with Delay, it can be a bit clumsy because the timing is never exactly the way you want it to be. Additionally, it's dependant somewhat on the object pre-existing. So, it may or may not work.
3) Utilize the WaitNNN methods within your keyword test. THIS is my favorite option. Now, I could describe it for you in detail here... but thankfully, the guys at SmartBear already wrote up how to do this in their online guide. Read the whole article but the stuff you'll be most interested in is at and around https://support.smartbear.com/viewarticle/68268/?q=wait+for+object#KDTTimeout
Hope this helps!
I send you a keyword test "AssignationEssais"
the test stop on the error at --TextnodeTestComplete-- because this field is suppose to be visible on screen to select a choice in the autocompletion list, and playback does not active the TextnodeTestComplete so it is impossible for TestComplete to click on it.
Note : We have changed the extension of the keyword test so you can get the information.
Thank you for response
