Forum Discussion
OK, as for the Accordian component, I'm not sure what native support TestComplete can offer to work with it other than the basics of Click and Keys. I'd have to examine the properties a bit more closely. What do you need to do with it?
As for the rest of your document... that's object recognition errors. The "Object does not exist" type errors you report are a problem with the accordion object itself but, as the errors indicate, one of the parent objects in the hierarchy is not being identified properly.
Aliases.browser.pageConstructionline.panelAppInitPageLoaded.panel.panel.section
You need to take a look at the mapping of that object, the properties being used, and adjust those properties so as to make a reliable identification. As is mentioned frequently here on this community, while the automatic mapping of objects by TestComplete is a good starting point, almost ALWAYS you should go back and rework the mapping to be more reliable. My guess is that the "section" object indicated is using some sort of property that changes dynamically from test run to test run and so cannot be identified. Alternatively, there may be more than one "section" in the hierarchy that matches the properties so TestComplete gets the first one it finds which might not be the proper one. You should go through the entire hierarchy of your object tree and validate the properties being used to map the component so as to give a good, reliable mapping. Please read through https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/overview.html for everything there is to know about NameMapping.
Side note...
While the NameMapping of the item can remain
NameMapping.Sys.browser.pageConstructionline.panelAppInitPageLoaded.panel.panel.section.panelContainer.panelRow.formFormNgPristineNgValidNgValid.panelAccordiongroup9428Tab.panelAccordionHd
You really should edit your Alias. The only true parts of the Alias that are meaningful are as follows, just as a best guess
Aliases.browser.pageConstructionline.panelAccordionHd
This will make your application test much more manageable.
Hello,
Thanks for your replay. I am gradually getting there.
"My guess is that the "section" object indicated is using some sort of property that changes dynamically from test run to test run and so cannot be identified. " - You are right with this. It changes dynamically from test run to test run.
When I drill down manually to the object behind the field I want to select it is never stable it keeps changing. If I select the object before this it points to a different field
What i want to do with it is that;
I want to be able to click on the drop down button on each row and type into the text-box displayed or select options display in the in drop down or click on a radio button or attach a document. Please see attached.
- tristaanogre7 years agoEsteemed Contributor
You need to fix the mapping of the section object. If the property being used is changing dynamically, then you need to find another property or set or properties that will more accurately identify the object. Until that is corrected, nothing else you attempt to work with on that Accordion object will work properly.
Related Content
- 2 years ago
- 11 years ago
- 12 months ago