Forum Discussion
That is a pretty good run down of how to do this task in TestComplete. I would suggest, for your timing, use the HISUtils.StopWatch object to start and stop the timer.
Caveat:
The result of the action, as you said, is something updated on screen. What this means is that TestComplete will need to find the object, check the necessary property, etc. This takes processing time. So, you're timing is going to include some of the overhead of TC doing that level of processing. This may be a matter of a few milliseconds or could be longer depending upon the timeout settings you use in your WaitProperty or WaitAliasChild or whatever methodology you use for the detection. So, as long as you're not looking for a 100% ACCURATE (e.g., "It takes on average 15 seconds for the query to return") measurements (more likely, "It takes on average 15 seconds for TestComplete to detect the query returns), that should work.
Suggestion: Look into AQTime as a performance measurement tool. That does a bit more profiling stuff rather than having to work specifically with the object identification.
Related Content
- 12 years ago
- 2 years ago
Recent Discussions
- 3 days ago
- 3 days ago
- 6 days ago