by sdaly » Wed Sep 21, 2011 10:25 am
I'm not sure the exact info you want, but here is what I do when starting out on a new framework....
First you will prob want to create a shared library (or code modules if using Studio) for all the common things you need to do while running tests. This can vary depending on the project, for example we have a shared dll which contains classes for working with databases, xml, the registry, disks, processes, services etc - because our apps involve manipulating these so we need to be able to validate.
You should then break down what apps you are trying to test, are the apps all separate and standalone? If so then create a solution or separate project for each app to test. If multiple apps are part of the same product being tested, then create one solution or project. You can then start to break down the product into the key areas, maybe create a class for each of these areas - for example FlexSite for the flex site and CFSite for the ColdFusion site. In each of those classes then you can write methods such as LogOn(), LofOff() etc. As these classes grow, you may wish to refactor them into finer classes or use namespaces to split the functionality into logical areas.
Hope that helps!