Microsoft Test

Manager 2013

Why MTM?
Test Tool
Different test types
Manual/scripted
Exploratory
Automated (CodedUI/Unit tests)

Integration

Visual Studio 2013 ALM

Source
Repos

Agile
Planning

Team
Rooms

Test Case
Management

Feedback
Management

Build and
Continuous
Integration

Team Foundation
Server

Resources
Visual Studio 2013
Ultimate/Premium/Test Professional
TFS
Visual Studio Online
Brian Keller http://aka.ms/almvms

Agenda

Test
Planning

Test Case
Managem
ent

Test Run

Explorator
y Testing

Lab
Managem
ent

Ready?

TEST
PLANNIN
G

Overview
1

Test plans

Test suites

Test configuration
and test settings

Testing Hierarchy

TEST PLAN

Test Plan

Test Plan Creation

Test Plan Creation

Test Center
Define tests you plan to run for a
specific sprint/iteration
Execute the tests from your plan
Measure progress/quality

Test Plan Properties

Test Plan Run Settings

Create Test plan from Web

TEST PLAN DEMO

TEST PLAN SUITES

Test Suites Overview

Test Suites
Static Test Suites
Query-based Test Suites
Requirement-based Test Suites
Copying Test Suites
Cloning Test Suites

Test Suites
Group your test cases into a hierarchy of
test suites
Root node (suite) contains all other test suites

Test Suites
Static
Contains test cases and other test suites

Query-based
Contains test cases based on a query
Test cases that fit the query criteria are
dynamically added
Cannot contain other test suites

Requirements-based
Group your test cases by requirements
Based on the work items that belong to the
Requirement category (Requirement, Product
Backlog Item, User Story, etc.)

Adding Test Cases to Static Test

Suites
Add existing or create new test cases for
your static test suites

Query-Based Test Suites

Query-based test suites are defined by work item
queries that select test cases
Example: All test cases with priority = 1
Any new test case with priority set to 1 will be dynamically added to
the test suite

Requirement-Based Test Suites

Add existing requirement (work item) to
your test plan to create test suite
Each requirement has its own suite
Test cases added are linked to requirements
Helps to determine test coverage and
completion of your requirements

Create Test Suites from Web

Interface

Copying Test Suites and Test Plans

Copying
Copies test cases by reference. New suite
shares same test cases
Useful for testing with different test plans but
same test cases
Can be done from the GUI

Copying Static Test Suites

Cloning Test Suites and Test Plans

Cloning
Copies test cases by value. New copies of
test cases are created
Useful for testing two different releases
simultaneously
Command line

Cloning Test Suites and Test Plans

Cloning Test Suites What Gets

Cloned?

TEST SUITES DEMO

TEST
CONFIGURATION
AND TEST SETTINGS

Test Configuration and Settings

Overview

Test Configurations
Creating Test Configurations
Defining Configuration Variables
Selecting Test Configurations
Test Settings
Diagnosis Data Adapters

Test Configurations
Configuration
variables specify
setup required
for testing
Examples:
Operating
system,
browsers,
software,
hardware, SP,
anything

Can be
associated with
test plans,
suites and test
cases

Create Test Configurations

From Test
Plan Run
Settings

From
Organize tab

Defining Configuration Variables

Selecting Test Configurations

Set default configuration(s) for your test plan
You may override at test suite and test case levels

A test case and test configuration pair is a

test point
Test results are saved for each test point

Test Settings
Test settings use diagnostic data
adapters to collect data when running
manual tests, automated tests, or both

Test Settings

Test Reports
View test run results in real time in MTM
Use predefined test reports (Microsoft
Excel, SQL Server Reporting Services)
Create your own reports (Microsoft Excel,
SQL Server Reporting Services)

Reporting on Test Progress: Test

Plan

Reporting on Test Progress

Test Case Readiness: Shows how many
test cases are in Design vs. Ready

Reporting on Test Progress

(continued)
Test Plan Progress: Tracks how many tests
have been run and how many are failing

Reporting on Test Progress

(continued)
Healthy version vs. unhealthy version

Healthy version

Unhealthy version

Reporting on Test Progress

(continued)

TEST
CONFIGURATION AND
SETTINGS - DEMO

TEST
CASE
MANAGE
MENT

Overview
1

Manual Test Cases

Test Steps
Parameters

Shared Steps

MANUAL TEST
CASES

Manual Test Cases

Test cases are work items
Test results are saved on each run
Manual test cases contain test steps
(test script)
May contain test steps with validation
A tester indicates pass or fail at the test
step level

A test case can be assigned to a tester

Manual Test Cases (continued)

Test cases can be added to multiple test
suites in the same or different test plans
Test cases are associated with 1..n test
configurations
Creating 1..n test points

Team Project
Test Plan
Test
Suit
e
Test
Cas
e

Test Suite
Test
Cas
e

Test
Cas
e

Test Plan
Test
Suit
e
Test
Cas
e

Test Suite
Test
Cas
e

Test
Cas
e

Test
Cas
e

Test
Suit
e
Test
case

Create Manual Test Cases from

MTM

Create Manual Test Cases from

MTM (continued)
Add test steps using Microsoft Test Manager (MTM),
Microsoft Excel, or Microsoft Word (via copy and
paste)
Add test
steps using
Microsoft Test
Manager
(MTM),
Microsoft
Excel, or
Microsoft
Word (via
copy and
paste)

Create Manual Test Cases from Web

Interface

Create Test Cases from an Assembly

of Automated Tests
Use tcm.exe
You must use a lab environment
Make sure that the test project is a
part of your build definition
The test cases will have the same
names as the test methods

Assign Test Cases to Testers

Individually or in bulk
Assign at test point level

TEST STEPS
PARAMETERS

Test Steps Parameters

Parameters
allow a manual
test case to run
multiple times
with different
data
Example:
@username,
@password

Parameters can
be added to
actions or
expected results

Test Steps Parameters (continued)

Overall test results are based on all
iterations passing

SHARED
STEPS

Shared Steps
Used for repeated sequences of steps,
such as logging in, that occur in many
test cases
Avoiding having to enter these sequences
again and again, createshared steps

Create Shared Steps

While youre editing a test case, select a sequence of
steps that you want to share
Steps you selected are replaced with a link to the
new shared steps work item

TEST CASE
MANAGEMENT DEMO

TEST
RUN

Overview
1

Running manual test

cases

Action recordings

Reporting bugs

Running Manual Test Cases

Run individual tests or entire suites
Create action recordings
Used for future runs
Action recording can be used in CodedUI
tests

Submit new bugs or update existing bugs

directly
Attach comments, indicate pass or fail,
take screenshots
Test case management features also
available in Web Portal

Running Manual Test Cases

(continued)

Action Recordings
Record a manual test (or shared steps)
to allow for a later run of certain parts
of manual tests
Example: Login, entire smoke test

Use it to help with:

A test that you will want to run multiple
times
Different manual tests that contain
common steps via action recordings
Automate by importing it to a Coded UI
Test

Creating Action Recordings

Playback Action Recordings

Preview Steps Before Playback

Submitting Bugs
Submit a bug from Test Runner
Information automatically added about
the test environment, comments,
screenshots, video recording

Submit a bug from Test Manager

when you view the manual test
result
No diagnostic data added via this route

Submitting Bugs (continued)

TEST RUN DEMO

EXPLORA
TORY
TESTING

Exploratory Testing
Test the application without a
predefined test script
Record screenshots, comments,
attach files, video and audio
narration
Submit bugs you find while testing
Includes rich diagnostic data collected
through testing
Uses the recorded steps to create a
manual test case

Exploratory Testing (continued)

Explore the application selecting a user
story/requirement
Bugs created will be automatically linked to the user
story/requirement

Explore the application without selecting a user

story/requirement

Exploratory Testing (continued)

Update comments, add screenshots
and files as you work, or add a bug

Exploratory Testing Sessions

EXPLORATORY
TESTING - DEMO

LAB
MANAGE
MENT

Lab Environment
A group of computers that you manage
as a single entity
Lets youcollect diagnostic datafrom
all the machines in the lab while youre
performing your tests. The data, such
as event actions, are attached to the
test results and to any bug that you
create
Automate the process of building,
deploying, and running automated
tests on your lab environment

Lab Environment

Standard Lab Environment

Both physical computers and virtual
machines can be added to a
standard environment
On each machine:
Configure a user account and a
password that has administrative
privileges. All the machines must have
the same username and password. It
doesnt matter whether the account is a
domain or a local account
Make sure that file sharing is enabled

Standard Lab Environment

(continued)

Standard Lab Environment

(continued)

Define the environment by adding the

computers. Enter the fully-qualified domain
name of each computer
Set the role of each machine

Standard Lab Environment

(continued)
When the environments status is ready, this means that
test agents have been installed on each machine, and that
they are communicating with your team projects test
controller. The test agents let youcollect diagnostic data
from its machines while you run your test

Use Standard Lab Environment

Mark the environment as in use to
assign it to yourself
Connect to the environment

Use Standard Lab Environment

Log into its machines and install the
latest build of your software

Use Standard Lab Environment

In testing Center, plan, properties, set the test
environment to the environment you chose.
This allows you tocollect event logs and other
datafrom the machines in the environment

Thank
you!
Raluca Suditu
raluca.suditu@gmail.com
http://ralucasuditu-softwaretesting.blogspo
t.ro/