Quick Start Guide for Automating Build, Deployment, and Test
[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]
This is a Quick Start guide for Lab Management. The guide helps you get up and running quickly by describing how to use virtual environments for automating daily build, deploy, and test cycles. The following procedures describe the key steps for this Quick Start guide:
Check-in application source code along with a unit test
Create a build definition
Create automated test case, test suite, and test settings
Create a workflow for build, deploy, and test
Queue the workflow
Before you start these procedures, complete the Quick Start Guide for Virtual Environments. Make sure that an environment has been created with a clean snapshot as described in that guide.
Check-in application source code along with a unit test
To check-in source code and unit test
Click Start, All Programs, Microsoft Visual Studio 2010, and then click Microsoft Visual Studio 2010.
Create a new team project or use an existing team project that contains the source code for your application.
On the View menu, click Team Explorer
In Team Explorer, double-click open Source Control. Map the local path for source control if you have not already done this. Check in all the source code into source control if you have not already done so.
If you do not have unit tests associated with this project, create a new basic unit test:
On the Test menu, click New Test.
In the pop-up dialog box, click Basic Unit Test.
When you are prompted, type a name for your test project.
Open and edit the source code for the unit test in Solution Explorer.
Create a build definition
To create a build definition
In Team Explorer, right-click Builds, and then click New Build Definition.
In the new build definition wizard for new build definition, enter the required information:
On the General wizard page, type the name for the build definition.
On the Build Defaults wizard page, select a drop location where the binaries generated from compilation can be stored. This folder should be a Windows share that has write permissions for the build agent, and read permissions for everyone.
On the Process wizard page, expand (Required), click Projects to Build, and then click the solution file for your application.
On the Process wizard page, expand Agent, click Agent Requirements, Name Filter, and then click the build agent that must be used for compilation.
Do not use the build agents that are installed in the virtual environment for compilation. They are used for deployment.
Save the build definition.
To verify the build definition, in Team Explorer, right-click the build definition, and click Queue New Build. In the pop-up dialog box, click Queue.
Create automated test case, test suite, and test settings
To create automated test case, test suite, and test settings
In Team Explorer, expand the node for your team project, then right-click Work Items under your team project, and point to New Work Item, and then click Test Case.
On the New Test Case page, in New Test Case, type a title for the test case.
Click the Associated Automation tab, click the ellipsis (…) button, click the unit test to associate, and then click OK.
In Microsoft Test and Lab Manager, click Testing Center. Create a test plan and test suite if you have not created one. For more information, see How to: Create a Test Plan.
Add the automated test case to the test suite.
In Microsoft Test and Lab Manager, click Lab Center, Test Settings, and then click New to create a new test setting.
In the new test settings wizard, follow these steps:
On the General wizard page, type the name for the test setting.
Select Automated for the type of tests.
On the Roles wizard page, select the correct combination of roles that represents your environment. From the list of roles, select the role on which tests must be run.
On the Data and Diagnostics wizard page, select the collectors that are appropriate for your environment.
Save the test settings.
Create a workflow for build, deploy, and test
To create a workflow for build, deploy, and test
In Team Explorer, right-click Builds and then click New Build Definition.
In the new build definition wizard:
On the General wizard page, type a name for the build definition.
On the Build Defaults wizard page, type the location of the build drops.
This is the location where the binaries generated from compilation are stored by the build agent.
On the Process wizard page, click the LabDefaultTemplate from the list of build process files.
To specify the settings for the workflow, select the Workflow Settings column, and click the ellipsis (...) button.
In the Lab Workflow Parameters dialog box, follow these steps:
On the Environment wizard page, select the virtual environment that you created. Also, specify the snapshot to which the environment should be reverted to before the build is deployed.
On the Build wizard page, click the build definition that was created earlier for compiling the application.
On the Deploy wizard page, select the option to Deploy, and enter the scripts that should be run on each virtual machine of the environment.
On the Tests wizard page, associate the test suite and test settings that should be used as part of the workflow.
Click Finish to close the Lab Workflow Parameters wizard. Save the build definition.
Queue the workflow
To queue the workflow
In Team Explorer, right-click the workflow definition that you saved, and then click Queue new build.
When prompted, click Queue.
This initiates a build-deploy-test cycle. After the source code is compiled, the environment is reverted to the selected snapshot, the build is deployed onto the virtual machines of the environment by running the specified scripts, and finally, the automated tests are run.
At the end of the execution, view the build report and log.