Why you don't want to use regular object repository? I have application with 500 screens, and it works fine except some dynamic objects.
On Thu, Jan 22, 2009 at 3:04 PM, alll fun <[email protected]> wrote: > Hi Everybody, > > Being a mute spectator of the group, I would like to ask a question from my > part too about repositories in QTP. > I have my own framework (though its simple) without the usage of object > repository and using the Description.Create method to capture the objects > with its unique properties. > The object properties has been parameterized throughout.... Since the > application has about 25 different screens (every navigation is treated > with different name by the developer :( ) the parameterization through > Datatable is bit slow at times. Some one was saying to look at the XML > repository method. > > Have anybody used such repository type? How far it is helpful in > "Description.Create" kind of programming. I googled for this but results did > not make me happy. > Any help on this is highly appreciated. > > -- > With Cheers and smiles... > Swaminathan.S.P > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
