Basically, you should look at your unique situation (automation environment, testing tasks, application being tested) and come up with a list that is tailored to you. For example, at my office, we have a specialized winform application that can work on multiple clients connecting to a central database. I have a function library that is specific to reporting system resource usage (memory consumption, processor utilization, etc) so we can report if the application seems to have a memory leak. There is another library that we use for tasks that deal with accessing Quality Center information. I also have other libraries and try to keep them grouped together based on their purpose. You can have one that deals with file system, another for generating unique data, and yet another one for some other purpose. The main reason for all the function libraries is a central location to change that will update to all scripts that use the functions. I also like them since it reduces the lines of code in my QTP scripts.
Maybe this will give you a starting point.
JohnBoy
Maybe this will give you a starting point.
JohnBoy
