Does any one have any information on how WR performs with a large amount of
GUI files loaded.
Or, what would be better to do, create few huge files or many small ones.
I am only concern about the performance issue.
My best guess if you wanna execute GUI verification point break it into separate files according to your testing needs and execute only those not all. If its one single piece then it takes more time for execution and managing is difficult nad u r loosing time too.
Oleg, I believe I heard it was better to break them up into small function groups and load them as needed. Not exactlly sure were I heard it,I wanna say it was from Mercury. The thing about performance will have to do with memory. GUI files can become very large and when you load them, you are using a lot of RAM. So if RAM is not a big issue I wouldn't worry about it. On the other hand if you do not have a lot of RAM I would suggest breaking up the files.
We are testing web pages on and decided early on to make individual gui maps for each webpage. We were wondering wether its better to load in the GUIs for all the webpages accessed in the script right at the beginning of the script (where they are manageable and easy to check on) or open them at relevant parts of the script and close them as soon as they are no longer required.
We have gone with the first option but I'm still curious as to which is better practice and why. Does anyone have any comments on this?