Dedicated testing tool that allows manuals tests plan, test cases, file bugs, create bugs in TFS for quality assurance team. This article demonstrates how to use the Microsoft Test and Lab Manager in Visual Studio 2010 to manage test suites and test cases. This article is based on the Application Lifecycle Management Hands-on Labs. That article will include end-to-end software testing capabilities of Visual Studio 2010. This includes a deep look at manual testing, lab management, data diagnostics adapters, the "actionable bug", functional UI testing, test impact analysis, test automation, and much more which will help you more easily find and eliminate defects from your software.
After wasting years not leveraging its huge developer's community to spread virtualization in every corner of the world, the company is finally moving on. Announced in November 2008, the integration between Visual Studio 2010, System Center Virtual Machine Manager (SCVMM) 2008 and Hyper-V 1.0/2.0 for virtual lab automation scenarios is now a reality called Visual Studio 2010 Lab Management.
Lab Management in Visual Studio 2010 provides an integrated development and testing platform for end-to-end virtual lab management. Lab Management enables development and quality assurance teams to work together more effectively to optimize the build process and minimize regression-testing efforts. It helps reduce costs associated with setup, teardown, and restoration of complex virtual environments to a known state for build automation, build deployment, and test execution.
Visual Studio Lab Management lets you manage a collection of virtual machines, templates, and virtual environments for your Team Foundation team project. You can use these environments to develop, test, or run your application. A virtual environment is a collection of virtual machines (VMs). Each VM in a virtual environment represents a role required for the application that you intend to develop, test, or run. For example, you might be developing a multi-tiered application that requires three roles: a desktop client, a Web server, and a database server.
When you create virtual machines from the golden master to represent a specific role that is required for a tier in your application, you then use these virtual machines to create an environment that is based on the roles in your application, as shown in the following illustration.
The Visual Studio Team System (VSTS) Lab Management Team has recently started a blog that introduces to the virtual lab automation and the capabilities of Visual Studio 2010 that is well worth a subscription.
Here’s a small excerpt from their first article:
The lab management service in TFS uses System Center Virtual Machine Manager (SCVMM) for management of lab infrastructure and provisioning of virtual machines across multiple virtualization platforms. You get a copy of SCVMM with Lab Management.
Microsoft Test and Lab Manager is a Windows Presentation Foundation based rich client. The Lab Center in Test and Lab Manager allows you to
- Create and manage virtual or physical environments
- Take environment snapshots or revert to existing snapshots for virtual environments
- Interact with the virtual machines in the environments through environment viewer
- Define test settings for the environments
You can define test plans, test suites and test cases in the Testing Center and execute them on the lab environments.
You can use Lab Management to start all the virtual machines in the environment to run an application, or test an application. Lab Management uses System Center Virtual Machine Manager (SCVMM) to allow you access to virtual machines or templates in a library as your golden masters. These golden masters are created by using either Hyper-V or SCVMM. SCVMM is used to deploy the virtual machines and templates in your environments on the specified host group. For more information about Lab Management, see Using a Virtual Lab for Your Application Lifecycle. Lab Management integrates with Team Foundation Build to let you deploy your application to a virtual environment, and run tests after the build is deployed. For more information, see Deploying An Application to a Virtual Environment. You can also run tests at any time on your virtual environments by using Microsoft Test Manager. For more information, see Testing Using Virtual Environments.
To begin with, MTLM allows you to create Test Plans for a Team Project. These plans have configuration settings, start and end dates, tests (which are arranged into "test suites") and test results. You can have as many different test plans as you want for a given project with the same or different test plan owners.
The Run Tests page allows you to execute manual or automated tests and it also shows you the results of the last test run for the selected test suite.
When executing tests you are presented with the Test Runner. The Test Runner allows you to execute multiple tests at once and shows each test step in detail. In this figure I am in the process of filing a bug against the selected step to which I have attached a screenshot and provided a comment about the failure. Each step can be marked as passed or failed and when you file a bug against a test, all of the information about the test is captured.
Working with Lab Management
Microsoft Test & Lab Manager (MTLM). MTLM is included as part of Visual Studio Ultimate, but as a standalone product it is also included (and is the main part of) Test Elements. It is a professional functional testing tool that gives you the ability to write, run and execute manual tests and to track the results. It has no dependencies on Visual Studio but does require TFS. The Test Runner allows for easily executing tests and filing bugs with all of the information a developer needs to fix the bug -- and the tester does not have to do anything in particular to get this all to work. There are many more capabilities available to you with MTLM and hopefully this brief insight will get you excited about the possibilities and all of the other great features available to you with the testing tools in Visual Studio 2010.