How to structure a test project
I have experience in using QTP and Test Complete. Our business is trialling vs 2010 Test and I am at a loss as to how to structure test projects.
When I was using TestComplete, I would separate different "actions" into different vbscript functions within a scripting unit. Then the scripting units would divide between the major components of the application.
For example, the application under test administers surveys to participants.
So there were three scripting units. One for actions specific to the administration side (e.g. creating surveys, creating participants), one for actions specific to the participants side (doing the survey) and one for actions common to both sides (e.g. launching a web browser, logging in, logging out).
Can someone advise me how I am meant to set this up using the codedUItest functionality in vs2010?
Is each action meant to be a different file? i.e. login.cs
Re: How to structure a test project
The way we use it (which is not necessarily the correct way nor the only way) generally is to have one Solution per project containing all codedui scripts.
Underneath the Solution node, we have one Project for each major functional area or just a single Project containing all coded ui scripts for smaller projects.
Within each Project, we have one CodedUITest file for each individual test.
We also use specific naming conventions and use folders to be more granular.
Hope this helps