QTP tries to make an object identification simple and, as a result, more stable, if for find an object QTP would relay on original DOM hierarchy, any change in the table will fail the script, you need also to find a way to indentify properly the table. You also have an option to play with it, for example if you have Page.Frame.WebButton.Click, you can use Page.Button.Click (you need to place the button in a proper place in Obj Repository.
On Wed, Dec 9, 2009 at 4:44 AM, Daim <[email protected]> wrote: > When I use the object spy, I get the following hierarchy for an object > > Browser.Page.WebTable.WebElement > > But when I add the same object in QTP, the hierarchy is added as > > Browser.Page.WebElement > > Why is the hierarchy different? Can anyone explain? > > Regards > > -- > You received this message because you are subscribed to the Google > "QTP - HP Quick Test Professional - Automated Software Testing" > group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<mercuryqtp%[email protected]> > For more options, visit this group at > http://groups.google.com/group/MercuryQTP?hl=en -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
