Forum Discussion
william_roe wrote:
You might be able to get 80% there with automatic mapping. For our SPA (single page application) applacation the Frames are the key element to map ahead of time and put wildcards in the appropriate place(s). I would be willing to go fully automatic if renaming worked better. I've found when renaming mapped objects that property checkpoints don't get updated.
I will NEVER AGAIN use extended find. I can't tell you how much time this "feature" has cost. YMMV
I am not sure, if I understand you correctly.
1. Did you map the elements via script? e.g. opening the page whose elements should be mapped and then started some script, that mapped all the elements to the namemapping file?
2. what problems with extended find did you have? We could not live without it... The namemapping must be horrible without it! It is sometimes slow but the test is really readable.
jsc wrote:
william_roe wrote:
You might be able to get 80% there with automatic mapping. For our SPA (single page application) applacation the Frames are the key element to map ahead of time and put wildcards in the appropriate place(s). I would be willing to go fully automatic if renaming worked better. I've found when renaming mapped objects that property checkpoints don't get updated.
I will NEVER AGAIN use extended find. I can't tell you how much time this "feature" has cost. YMMV
I am not sure, if I understand you correctly.
1. Did you map the elements via script? e.g. opening the page whose elements should be mapped and then started some script, that mapped all the elements to the namemapping file?
2. what problems with extended find did you have? We could not live without it... The namemapping must be horrible without it! It is sometimes slow but the test is really readable.
#jsc
1. We currently map the field(s) we are going to use in the keyword test via the object browser
2. Extended find caused us memory issues. The Chrome hook would grow to nearly 2gig and stop responding.
We prefer reliable testing over ease of test creation.Playback speed also seems better without extended find.
- jsc9 years agoRegular Contributor
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
- Colin_McCrae9 years agoCommunity Hero
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
- 11 years agoKateryna
- 4 years agomehdisinger
Recent Discussions
- 6 hours agoSvetaG