Reconciling testers and developers with Visual Studio 2010 (by François Merand, Sogeti) A new tool: Test Manager 2010


Test Manager 2010: test plan management

The 2010 range brings a new tool, intended for professional testers (generalists and functional): Test Manager 2010. This tool connects to a TFS 2010 server, such as Visual Studio, to store all the information useful for testing, and also to share information with developers (work item tracking, among others).

Test Manager gives access to two separate modules: The“Testing Center“, which allows you to create and manage your test plans, the“Lab Center” to provision and administer physical or virtual machines and run your different test plans. This file will deal with the“Testing Center” part.

Access to the Testing Center and Lab Center modules. Microsoft

Using the tool is quite simple: the main menu is displayed at the top and contains four sections:

1. Plan: to design and organize one or more test plans (campaigns) in TFS 2010, for the different development projects in progress. It is from this section that you will have visibility on the test cases you have to manage.

2. Test: the next step, which will allow you to execute your various tests and also to collect the results in order to report any anomalies detected to the development teams for example.

3. Track: to coordinate your test campaigns and the different builds (versions) in progress. This tab also gives you the possibility to see the tests still to be executed and to access the reporting module.

Organize: a toolbox to help you better organize the content of your tests, such as the ability to declare actions that are common to several tests and then reuse them in a single step (shared steps).

Manage tests via dashboards

In concrete terms, the test cases defining the test plans are work items stored in TFS 2010, and therefore shared with the developers. They can consult them from their Visual Studio in the Work Items section.

In the end, the Testing Center allows you to manage your tests via dashboards and to determine at any time, for example :

which sections have the most failures,
the number of tests remaining for a given iteration,
the success (failure) rate in a campaign,
how to reallocate your resources on a campaign,
bad test configurations (those with the highest failure rate),
etc.

It is also with this tool that a tester will be able to transmit a bug encountered during the testing phase to a developer by creating a work item.


Leave a Comment