Unable to find object

[msalvador]

Hi guys,

I use TC 14.0, and at the moment my browser is Chrome, but my webapp can run in IE or firefox.

I map manually objects, because using recording mode I found different Issues.

My web app is one, but can run on different ips, obviously must show the same results for each ip.

My problem is that a lot of times when I test my code and I run in ip(one), everythings is ok but if I switch in ip(two), objects are not found.

Below a typical example:

Unable to find the following object when executing the Click command:

Aliases.​browser.​pageVersionlogreport.​panelWrapper.​panelShowcase.​panelInfo.​formViewlistform.​submitbuttonSearch

Reason

The parent object was not found:

Aliases.​browser.​pageVersionlogreport.​panelWrapper.​panelShowcase.​panelInfo.​formViewlistform

[cunderw]

Look at the properties you are using fo find ​formViewlistform in your namemapping and them compare that to what you see in the object browser between the two different environments. There is likely something that is not static that you will need to account for.

[msalvador]

Hi cunderw,

I attach my object with attributed, how can I understand if I have a non static parameter?

[cunderw]

Can you also provide a screen shot of the object browser with object selected?

[msalvador]

You mean this?

[cunderw]

Not quite, on the left pane where your logs are there is a tab at the top called object browser. You need to find your object that is not being found in there.

[cunderw]

Ok, so it looks like the panelShowcase is where it stops working with your mapping. Provide similar screenshots for that object.

[msalvador]

Panelshowcase.

How can I understand if I use static params? and how can I set TC, in order to do not fill static params?

[cunderw]

Also need to see the namemapping for that object.

What is probably happening is some property that is being used to map the object has slightly different values between the two environments, so you have to compare and adjust by picking a different property or wild-carding it. There is no possible way to make test complete 100% resiliant to this automatically. It does it's best guess, but 99% of the time you will have to manually adjust the properties of your mapping criteria.