Forum Discussion
Hi william,
we have memory issues too, but not (afais) with the chrome hook, but with TestComplete itself (taking 1.2+ GB RAM). I opened a support case and now got a response... hopefully it is fixed.
Our test with extended find runs perfectly fine. Maybe your application / namemapping tree is much larger than ours.
So I cannot be lazy and let a script do the mapping... I will have to do it myself. grml
Best regards,
Joachim
You can right click on an object you already have in your map and there is a "map all child objects" option for it.
So you can go object by object, layer by layer.
No exactly what you want, but maybe better than one by one. I'm not convinced though. I use your current method of doing it manually. I do the high level, core items, initially, then add detail as tests are built. I also use helper functions so find smaller, lower level, objects on the fly during run time. And a well thought out Alias map.
I also don't like extended find as it can hide problems.
And I've never liked "add everything" type mapping options. QTPro let you do that. We spent more time tidying up the huge horrible mess it created than we saved by grabbing everything at once in the first place .....
- jsc9 years agoRegular Contributor
ok, I stick with my current method.
Related Content
Recent Discussions
- 4 hours agojstaehlin
- 21 hours agoAivanitskiy