should I use one repository file for the whole application?

Ask general questions here.
Ruser
Posts: 24
Joined: Wed Oct 07, 2009 3:26 pm

should I use one repository file for the whole application?

Post by Ruser » Tue Oct 27, 2009 10:18 pm

I have a big application under test here,

one script I just made, covers a couple of test cases, has over 200 objects in the repository.

I believe if I put all the objects in one repository for this application, it should have more than 2000 objects.

My question here is, should I use one repository file for the whole application? Is it gona affect the replay since Ranorex will search particular object in each step? I also found maintain such a big repository is a headache.

If I use different repository for each individual automation script, then I will have to do a lot of update if an object changes during the release.

What's your suggestion here?

Thanks,

Ruser
Posts: 24
Joined: Wed Oct 07, 2009 3:26 pm

Re: should I use one repository file for the whole application?

Post by Ruser » Thu Oct 29, 2009 3:46 pm

welcome any thoughts.

do you use one repository file for the whole application or each automation script has its own repository

User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: should I use one repository file for the whole application?

Post by Ciege » Thu Oct 29, 2009 4:14 pm

Ruser wrote:welcome any thoughts.

do you use one repository file for the whole application or each automation script has its own repository
I for one do not use any repository at all. I find all my objects when needed.
Not that this answers your question, but if you find the repository to be too daunting you can live without it.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

Ruser
Posts: 24
Joined: Wed Oct 07, 2009 3:26 pm

Re: should I use one repository file for the whole application?

Post by Ruser » Thu Oct 29, 2009 7:31 pm

you must be using visual studio to create your test framework, right?

We are using Ranorex Studio and use record a lot, need to build and maintain a repository here.
Ciege wrote:
Ruser wrote:welcome any thoughts.

do you use one repository file for the whole application or each automation script has its own repository
I for one do not use any repository at all. I find all my objects when needed.
Not that this answers your question, but if you find the repository to be too daunting you can live without it.

Ruser
Posts: 24
Joined: Wed Oct 07, 2009 3:26 pm

Re: should I use one repository file for the whole application?

Post by Ruser » Thu Oct 29, 2009 7:35 pm

also, when the UI/Xpath changes, you still need to update all your scripts

If you have a central repository for all, or most of your script, you only need to update one file
Ciege wrote:
Ruser wrote:welcome any thoughts.

do you use one repository file for the whole application or each automation script has its own repository
I for one do not use any repository at all. I find all my objects when needed.
Not that this answers your question, but if you find the repository to be too daunting you can live without it.

User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: should I use one repository file for the whole application?

Post by Ciege » Thu Oct 29, 2009 7:48 pm

1) Yes, we use Visual Studio for all the Ranorex development.

2) I have no need for any "hard coded" or repository stored XPaths. My framework handles finding everything at runtime. For example, if I want to click a pushbutton, I call my pushbutton find method and provide the form I want to find it on and the name of the pushbutton (accessible name -or- text). The method then finds that pushbutton and returns the handle to it. I don't need to update my code for any changes unless the object goes away completely or a new object is inserted to replace the old object. In either case, even a repository would need to be updated for this.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: should I use one repository file for the whole application?

Post by Ciege » Thu Oct 29, 2009 7:53 pm

Just want to add, my method is not necessarily for everyone. But it works for me.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: should I use one repository file for the whole application?

Post by Support Team » Fri Oct 30, 2009 10:41 am

IMHO Ranorex users should use repositories, unless they really know what they are doing :-)
Ranorex repositores have some useful features built into them that help avoiding some common mistakes "not-ciege-experienced" users could happen to make. However, if you're creating your own Ranorex framework for your application, not using the repository might be more flexible.

And I recommend not using very large repositories, not for performace reasons, but since large repositories with hundreds of elements can easily get confusing for a user. Whenever something gets too large, it gets complicated and confusing. Try to keep your repositories small and simple; e.g. you could create a repository for every tab in a tabpage, for every dialog that pops up, or for every complex control. The choice is up to you, how many items you want to have in a repository, but as soon as you have the feeling that there are too many items which don't logically belong together, you should consider splitting the repository up.
Ruser wrote:you must be using visual studio to create your test framework, right?
We are using Ranorex Studio and use record a lot, need to build and maintain a repository here.
No, you can create your own framework around Ranorex with Ranorex Studio as well. Recordings and repositories can even help you a lot. A framework just means that you create some helper method for some often needed operation, and from then on you use that method instead of implementing that method again and again. So, if you create a recording for opening your application, and from then on always use that recording if you want to open your application instead of re-recording the needed actions again, you already built your own small framework.

Regards,
Alex
Ranorex Support Team
.
Image

Ruser
Posts: 24
Joined: Wed Oct 07, 2009 3:26 pm

Re: should I use one repository file for the whole application?

Post by Ruser » Mon Nov 02, 2009 4:52 pm

Thanks for your reply, support team. Which way do you suggest in building repository:

1) have a repository in each sub section of the application under test. in each automation script, include multiple repositories

2) have a repository for each automation script

thanks,
Ruser

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: should I use one repository file for the whole application?

Post by Support Team » Tue Nov 03, 2009 7:27 pm

I can't give you a general recommendation on that one. Just follow the rule I stated before: Whenever a repository grows too big, try to split it up into two or more logically separated repositories.

So you could start having a single repository in your automation project. But as your project grows bigger, you might need to split that single repository into several ones, each covering a specific aspect of your automation task.

Regards,
Alex
Ranorex Support Team
.
Image