Microsoft Test & Lab Manager Beta 1 – Test Plan

In my last post I talked about Microsoft Test & Lab Manager - Interface, in this post I’ll talk about creating new test plan.

But before we can create Test Plan we must connect to a Context to work on.

The first thing you will see is “Set Plan Context”, as I said in the last post – you can’t start working without a Plan!

If you already define plan for your testing team you can select those and if not create new Test Plan.

“New Test Plan” – Is very simple screen that allows you to define your testing plan for specific dates.

In the right side you will see that each Test Plan is assigned to specific Tester\Manager under the Owner Field.

Test Plan are usually written before the actual product releases, and for this reason you can define that State to Inactive.

Start date = when we are planning to start working on this plan and the end time when we have to finish this plan.

Under each Test Plan you can define Test Settings for two types of test – 1. Manual Test , 2. Automatic Test

Test Settings are not Test Configuration(Browser type or OS etc…), Using Test Settings you can define what kind of information you want to collect when running the test and where you want to run it.

You can create new Test Settings or edit existing Settings by select and click Open.

How do you want to run test?

Manually on my local machine
1. Manually and collect information from remote computer.
Automatic Test on remote server.

Data and Diagnostics

This is one of many great improvements: What and How much of data you want Microsoft Test & Lab Manager will collect while you running the tests…

Action Recording and Action Log – You can record your UI actions to create an action recording that can be played back later.You can also record the UI actions as text in a log file to review what actions you perform when running a test. those can also be added as extra information to a bug.

ASP.NET Profiler – Activate ASP.NET profiler and also profile database interactions.

Code Coverage – By adding program assembly you can get the Code Coverage % for each test.

Diagnostic Trace Collector – Events only, Records significant diagnostic event only which has minimal impact on performance.
Events, Methods and Parameters, Record method-level tracing which has potential impact on performance.

Event Log - Event logs to collect from the machine where the data collector is run.

Network Emulation – Select which network profile you want to use.

System Information – Collect System Information to be added as extra information to a bug.

Test Impact Collector - By using test impact analysis, you can identify the tests that you should run, based on coding changes that were made to the application that you are testing between builds

*** If you enable collecting test impact data, collecting code coverage data will not work.

Video Recorder – Record the Screen or specific application during the test,after test complete each step will be linked to his time line inside the video.