Microsoft Test Manager

This is the new standalone product introduced, but this is not a part of Visual Studio 2012 Premium. It is a part of Visual Studio Test Professional and Visual Studio Ultimate. This is the functional testing tool, which provides the ability to create and execute manual tests and collect the results. This tool works without Visual Studio but does require a connection to the Team Foundation Server and the Team Project.

The Testing Center is used for creating Test Plans and creating Test Suites and test cases for the Test Plans. We can also associate the requirements to the Test Plans. The other features such as running the manual test and capturing the Test Results and defects, tracking the Test Results using existing queries and creating custom queries, organizing the test cases and shared steps for test cases, and maintaining the test configurations , that are supported by Testing Center.

Lab Center is used to set up and create lab environments for the test execution. The environments are created by using the Physical and Virtual machines with set of configurations. Later the environment is deployed so that the test would be conducted using the specified environment.

Connecting to Team Project

MTM should be connected to the TFS Team Project to create the Test Plans and test cases. The first task in opening MTM is to connect to the TFS Team Project from the Team Project collection , as shown in the following screenshot:

Connecting to Team Project

Test Plans, suites, and test cases

The Test Plan window in the Testing Center allows the creation of new Test Suites, test cases, and adding test cases based on requirements. Any number of test cases can be created or added and configured through this window. The first step is to create the Test Plan and Test Suite. Each Test Plan contains a set of Test Suites which helps us to plan the testing effort. For example, we can create a Test Plan for each sprint, if we are using agile methodology for the software development. The following screenshot has one Test Plan (MytestPlan) with two Test Suites as Add Numbers Test and Second Test Suite:

Test Plans, suites, and test cases

The next step is to create or add test cases to the suite. The requirements can be added to the plan and then test cases can be associated to the requirements. In the above example, three requirements are added to the first Test Suite, Add Numbers Test and new test cases are associated with the requirements. These requirements are available in TFS under the Team Project. If we follow the Application lifecycle management and tools available in TFS then we should have the requirements created as part of the requirements phase already.

Defining test cases

The creation of a test case involves the definition of a lot of properties for it. Each testing step and the expected result should be defined. The user scenarios, links, and attachments can be associated to the test cases. The test case can be classified under the specific area path and iteration path for the Team Project in TFS. Other properties such as Assigned To, State, Priority, and Automation status can be set for the test case as shown in the following screenshot:

Defining test cases

Lab Center

The Lab Center in MTM helps us to create and configure different virtual/physical environments for our Test Runs, test settings such as defining the roles and configuring the data and diagnostics information for the selected roles, configuring the Test Controllers required for the test, and configuring the test library to store the environment information. The following screenshot shows the Lab Center without any environment:

Lab Center

We can see the details of these configurations later in Chapter 13, Test and Lab Center which explains the features of Testing Center and Lab Center.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.129.72.176