Forum Discussion
I already tried putting a delay before and it made no difference at all.
We could argue whether it makes sense that the second time is faster, but it doesn't make any sense that it takes so long to succesfully find a view that is already visible and in the first or second level of the root view.
The same behaviour is observed when using the fullpath of the object.
We could also argue that two seconds is not a long time.
- sergi9 years agoContributor
Marsha_R wrote:We could also argue that two seconds is not a long time.
I don't think that's arguable.. 2 seconds to find a view that is already there and only within 2-3 levels of children is insane. Especially when TC is able to find any other view within 50-60ms...
NisHera wrote:Which vertion of TC you are working with and what application you are testing?
10.60 and I'm testing a .NET+WPF application.
- Marsha_R9 years agoChampion Level 3
It's a good thing that I'm not testing TestComplete then! Two seconds out of my 70 minute test suite isn't worth pursuing.
- sergi9 years agoContributor
Marsha_R wrote:It's a good thing that I'm not testing TestComplete then! Two seconds out of my 70 minute test suite isn't worth pursuing.
Sure 2 seconds out of 70 minutes is nothing, but in my case, those 2 seconds (I have to interact about 45 times with a MessageBox) represent 90 seconds in a 15 minutes test, which is 10% of the time.
That's why I need to know why this is happening and I was hoping for an answer from TestComplete but seems like I'll have to open a support ticket..
Related Content
- 6 years agoanupamchampati
- 5 years agoadam81
Recent Discussions
- 2 hours agomacheshmeh
- 18 hours agomarkos