Forum Discussion
I have a function beofre this one that wont carry on till the grid is loaded, so hopefully it isn't the first suggestion.
I don't close the application each time as it would take up too much test time. The application doesn't take up much memory space but TestExecute 12 does.
Try, before your call of that If then, to do a RefreshMappingInfo of the parent object of the grid. That might do it.
- charles_16 years agoOccasional Contributor
I added the RefreshMappingInfo step but hasn't solved the problem.
- tristaanogre6 years agoEsteemed Contributor
One of the things that I've observed in working with grids in a VB application via TestComplete is sometimes there are back-end processing things that are occurring that are not easily discernable. A grid is displayed on screen and, based upon what I can observe of the grid, everything is where it needs to be so I proceed with my tests. However, all the rows are not populated right away because there is an SQL query that needs to complete... or the grid hasn't populated all the columns yet because it is still resolving some code that determines which columns to display... or the grid loads... but then the MDI component that embeds an internet explorer page on top of the VB application refreshes... Any number of things.
Just as a diagnostic test.... and I understand that this will extend your test execution time... but what would happen if, after you navigate to the form that has the grid, before you attempt any processing with the grid (variable assignment, etc), add a hard coded delay of 5 or 10 seconds... just to see what happens.- charles_16 years agoOccasional Contributor
will give it a try. I have been having several timing issues since upgrading TestComplete from v7 to v12 without changing the test scripts.
Related Content
- 2 years agojaredjamieson
- 6 years agoLAB
- 8 years agoacm