I change it to 15000 but no change seem so.
I will replace the ClickItem function by Click.
Thanks for your investigation.
Unfortunately, the TestExecute version of your log is coming up empty so it's hard to determine what's going on there. The TestComplete version I'm only seeing one line where anything resembling "ClickItem" is being referenced.
However, my best guess, based upon your description of the error message, is possibly one of several things:
1) A timing issue where, on your TestExecute machine, the item you are attempting to click on or even the control "linkManage" is not fully rendered when the test is attempted, hence a "not found" error. Solution - Increase the auto-wait timeout either globally on your project or (better solution) on the individual action in your keyword test
2) An environment issue where, on your TestExecute machine, a different version of the browser or other environmental factors is causing the item in question ("linkManage") to be recognized or rendered differently. Solution - Verify configurations between the two machines and make sure that everything is the same.
3) A mapping issues where, on your TestExecute machine, for some reason, your Alias mapping of your components is not the same as it is on your TestComplete machine, possibly due to an incomplete our outdated copy of the NameMapping file on the remote box. Solution - Pull down the latest project version to the remote box (usually done using some sort of version control system)
BUT... these are just guesses... without the actual log file from your TestExecute machine, can't really precisely give an answer.
I checked your 3 solution already but it didn't seem to be that :
1- Global wait time is already 13000
2- Browser version and other environement parameters seem correct
3- Project in Virtual Machine is exactly the same than my local copy
You can find the "not empty" log in copy.
Best regards,
In the screenshot that goes along with the error, I'm not able to figure out which object is being attempted to interact with in order to execute a "ClickItem" call. ClickItem is supposed to click on an item in another control where that item has either the index or the text that is being passed in as a parameter. So, for some reason or another, the object for whom you are trying to select "ClickItem" for does not exist or is not being properly recognized.
According to the call stack, the error is happening on line 6 of a keyword test. Could you post a screenshot of the keyword test, specifically with details for what is happening on line 6?
In the Web app, the link "Interventions", "Items" ,"Manage"... etc, contain sub elements :
So to call these elements, i use ClickItems : linkManage.ClickItem("User"), linkManage.ClickItem("Repair actions")... etc
What i don't understand is why these elements are recognized when i run in local with TestComplete but not when i run it in VM with testExecute... And for what i checked, it's happen with all tests with the ClickItems statement
Here is the screenshot :
Remark : I use TestComplete 11.31.2420.7 & TestExecute 11.11.1064.11
The object "linkManage" is being recognized in TestComplete as a Select control for which the "ClickItem" method makes sense. In your environment on your TestExecute machine, that is not happening.
Now... here's a point of interest. In the screenshot of your keyword test, the PageAll item is showing the Firefox icon... indicating, at least if I understand it correctly, that in that environment the browser being used is FireFox...
The screenshot in the error log shows that the test is being attempted against Internet Explorer.
It is ENTIRELY likely that there is a difference in object recognition between the two browsers. Is FireFox installed on your TestExecute VM and are you explicitly calling it? That would be my next line of investigation...
