Forum Discussion
Hi,
It is difficult to say something definite without knowing what you do with your tested application and how it behaves, but here are the generic considerations:
-- 'The object "ValueTable" does not exist' error message means exactly what it says. Most probably, you worked with this object before in the test and the object was destroyed (and, maybe, recreated) after some action. If this is the case, then you must search for and get this object again before you will be able to use it in test code.
-- Test code may be executed too fast while your tested application may need some time to create this or that tested object (for example, to get some data from the database). While TestComplete has Tools|Current Project Options|Playback>Runtime>Auto-wait Timeout option, sometimes you must explicitly wait for the object using one of the .WaitXXX() methods provided by TestComplete;
-- Note that there was a warning before the ''The object "AbstractTreeView_InternalJTree" does not exist' error in the log. This warning means that there were some problems while searching for the target object and it is a good idea to resolve those problems. As the message says, check the Additional Information log pane for more details as for what problem and for what object has occurred.
-- https://support.smartbear.com/screencasts/testcomplete/reliable-tests-for-dynamic-objects/ webinar recording from the https://support.smartbear.com/screencasts/testcomplete/ page might appear to be useful.
- Soumya7 years agoOccasional Contributor
Thanks.
This helps. 1 thing is that, just to make sure there is no change, i am opening the app freshly everytime.
I will try with wait option
- Marsha_R7 years agoChampion Level 3
Soumya wrote:
Thanks.
This helps. 1 thing is that, just to make sure there is no change, i am opening the app freshly everytime.
I will try with wait option
Are you also closing the app every time? If you aren't, then TestComplete may still be looking at a previous copy of the app and therefore not be on the objects that you expect.
- tristaanogre7 years agoEsteemed Contributor
My vote is a "timing" issue where your test is attempting to access an object that is not present in the application yet because the tests are moving faster than the application. I think you'll find adding Wait methods and other similar techniques will resolve the problem.