Hi Swaminathan,
How hard is to load object repository, and why it does your functions not
reusable?
There is no difference where and which format the object attributes written:
it can be binary OR, Excel table, VBScript code or XML. It is only different
way to store the same information.
But it isn't exactly true to say, that there is no difference. If an object
attributes are changing in runtime, it is different. Often we can handle
dynamic changes by using regular expression, but sometimes RE doesn't help.
Here is an example:
Static Object Description:
Set oDesc = Description.Create()
oDesc("html tag").Value = "IMG"
oDesc("image type").Value = "Plain Image"
oDesc("html id").Value = "cal.*BOseries::Calendar::.*::on_sale::0"
oDesc("micclass").Value = "Image"
oDesc("file name").Value = "cal.gif"
Dynamic Object Description:
Set oDesc = Description.Create()
oDesc("html tag").Value = "IMG"
oDesc("image type").Value = "Plain Image"
oDesc("html id").Value = "cal.*BOseries::Calendar::.*::on_sale::0"
oDesc("micclass").Value = "Image"
oDesc("file name").Value = "cal.gif"
* oDesc("index").Value = ActualIndex*
(* I have many such objects if user clicks "Add Element" button*)
In first case it can be saved in OR and be used by its logical name. It will
work within any function, in the second case the object can't be saved in
OR, so we have to use descriptive programming. In general, it's better to
use OR when it possible, it follows basic programming principles of data
encapsulation and modularity.
http://en.wikipedia.org/wiki/Information_hiding
http://en.wikipedia.org/wiki/Modularity_(programming)
In addition to it you save extra time by recording objects, by the end we
are working with automation tool, which should save our time. If I need
manipulation on all objects in OR, I export OR to XML, change it in text
editor and export it back to OR.
I don't believe, you have 100% dynamic application.
Roman
On Fri, Jan 23, 2009 at 9:00 AM, alll fun <[email protected]> wrote:
> Roman,
>
> The main idea of using the scripts without OR is to have my scripts
> dynamic.
> If i want to automate any other project I can just copy paste the common
> functions and finish the scripts just like that. This would save about 70%
> of the scripting time (considering that no new functions are required).
> So just in case thought of considering the xML repository. However I'm not
> sure whether XML repos. would help my scripts or not.
>
> On Thu, Jan 22, 2009 at 7:16 PM, Roman Zilber <[email protected]> wrote:
>
>> 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
-~----------~----~----~----~------~----~------~--~---
