mtm test management system

Immucor, Inc. All Content ©2010 Immucor, Inc.

Microsoft Test Manager Test Management Tool

Immucor, Inc.By: Minu Mishra


• Benefits• Modules and Microsoft Test

Manager Demo

Agenda


Centralized Storage & Repository Usage

Supports the entire testing lifecycle

Easy browser interface & accessibility

Requirement Traceability

Problem Management /Defect

Supports Test Script Automation

Report Generation (Graphs & Reports)

Status Tracking (Testing Progress / Defects)

Sorting & Filtering ability providing various views

Benefits


MTM uses following the modules, as illustrated below,To manage requirements, plan tests, execute tests andManage defects for remediation. Each module can be accessed by clicking on the New tab at the top of theMTM main screen:

– Requirements Management; – Test Case management;– Bug Tracking and Reporting; – Risk Management;– Change Management;– Issue Management;– Task

Modules


Add/Modify/Delete the requirement.

Overall status of the requirement (Reviewed/Not Covered)

Requirements are linked to the test case(s).

Requirements Module


Connecting To the Microsoft Test ManagerPre-Requisite: Visual Studio 2010 must be installed before using MTM.Microsoft Test Manager is accessible from any Immucor web browser using the following URL: http:atl-tfs01\


Getting Connected to MTM:

1. Ensure that the proper Project is selected from the Project List.

2. Click on

Note: The first time MTM is accessed; there will be a short delay while the required web objects are downloaded to the browser. This is a one-time activity as the objects are permanently stored in the browser once they are downloaded.


Getting Started With Microsoft Test Manager

Microsoft Test Manager

Microsoft Test Manager is an application that allows the user to control the following major facets of the testing process:

•Requirements Management; •Risk Management•Change Management•Issue Management•Test Planning: •Test Execution; and •Bug Tracking and Reporting.

All are controlled through a single browser-based application.


Select Work ItemsMicrosoft Test Manager uses multiple Work Items, as illustrated below, toManage requirements, plan tests, Issue, Task and manage Bugs for remediation. Each Work Item can be accessed by clicking on the New tab located on the Right

atthe top of the Microsoft Test Manager main screen: NEW


Once user is connected with the project click the New Tab located in upperright corner. When user click the “New” tab, a drop down list of work items isdisplayed.

Open Bug Work Item

New Work Items List


Requirements Module

A

B

C

D

E

Select the Requirement work item from the New drop down list.


• Requirement Item has Requirement Priority A which is based upon Criticality of the Requirement Risk – B.

• If the requirement is associated with the ETQ Document and has ETQ Reference Number C, enter that number in the field for traceability purposes.

• One or more Test Case(s) D can be attached by clicking on the Test Case Tab.• If the requirement has attachment(s) E the user will have the ability to attach

multiple documents, Screen prints, files, etc., as needed.• • Note: One Requirement can have multiple Test Cases attached but a Test case can

be attached or refer to only one Requirement. A Test Case can’t be associated or attached to multiple Requirements.

Requirements Module

REQUIREMENTREQUIREMENT

Test Case

Test Case

Test Case

Test Case

Test Case

Test Case

Test Case


• Test PlanningMicrosoft Test Manager can act as the centralized repositoryof all testing artifacts. The Testing Team scope includes thefollowing testing activities, all of which are managed usingMTM:

– Unit Testing;– Integration(code-based) Testing;– System Integration Testing;– Regression Testing; and– Data Integrity Testing;

Test Plan Module


Planning Tests Using Microsoft Test Manager


Add Test Plan window appears after Selection of Project,click on the Add Test Plan tab.

Test Plan Module


Enter a descriptive name of Test Plan. And click on The pre-populated folder structure for each functional area within the scopeof the application-testing project will be displayed.

Test Plan Module


A test suite can be added by Right clicking on theTest Plan;

Adding Test Suite to the Test Plan


Right Click on the Test Suite and Rename it if needed. User canEither add an existing test case(s) or create and add a new testcase by selecting the option to the Test Suite.

Adding Test Cases to a Test Suite


Right click on The Test Suite and select add a Test Case. Onceuser clicks on add Test Case from the Right Click drop down thena Query window pops up for the “Add Test Cases to Suite”.

Test Plan Module


Test Plan Module


Select or highlight Test Suite and click on button.“Add existingRequirement to this Test Plan” Query window will be displayed. Provideappropriate criteria and Run Query. Result will display the list of

Requirements.Select the Requirement and click on “Add Requirement to Plan” button.

Associating Requirement to the Test Suite


Open an existing Test Case or write a new test case then click on “TestedRequirement” Tab then click on icon. A pop window of “Add link to

theTest Case” will open up. Provide required information and add requirementsto the Test Case.

Linking Requirement to the Test case


Linking Requirement to the Test case


The status flag is used to track the position of each test case throughout thereview process. The diagram below illustrates the workflow for the change ofStatus of each test case:

Test Case Status Workflow


The Test module of Microsoft Test Manager Application will be used tocoordinate and track the execution of the test cases that were designed usingthe Test Plan module.

Test Run


–Bug Work Item(Defect Management)

Add/Modify/Delete the Bugs

Two ways to add a Bug: During test execution Manually

A test condition can be associated to multiple bugs but a bug can only be associated to one test condition.

Status tracking & reporting on the defects

Filtering capability will be extremely useful when searching for the bugs on a particular criteria. (e.g., High priority/Open bugs).

Bug Tracking Tool using Microsoft Test Manager


Bug Form


The testing Team will utilize the Bug work Items in the event of test failure or iferrors are detected during Testing.

Bug Work Item


Start the Microsoft Test Manager’s Test Run Utility• Click the button. • Start Test Window will appear. Click on Start Test in order to start the test

execution manually.

Test Execution


Bug Identification

Bugs should be captured when any application anomaly is encountered,unless the Bug is identical to one that has been previously identified andrecorded during the testing process. If there is a question as to whether theBug is the same as a previous Bug, the user should record the Bug and allowthe Test Lead to determine if there is duplication.

Bugs should be captured and recorded if:

o The actual result of a test step does not match the expected result;o A function of the application being tested is not working according to

specifications; oro A general problem, which is non-bug related, is observed within the

application.

Capturing and Recording a Bug


if the user is unable to record a Bug during test execution, the Bug may be submittedlater as follows:• Click on the New Button on the MTM main Screen. (A)• Select Bug from the List and highlight it. (B)• Click on OK.

Capturing and Recording a Bug

A B


Bug tracking form has mandatory fields which are highlighted. Dates arepopulated automatically. Text fields will be entered manually.

Bug Tracking Form


The Tracking Phase provides important information for evaluating the progressof current projects as well as for monitoring the overall quality process of anorganization resolved.

Bug Management Cycle


The Bug Status Management process begins with the detection of the bugand ends with the re-testing and closing Bug.

Bug Status Management Process


Bug tracking has following status:– New– Open– Fixed– Test– Passed

• Closed– Failed

• Open / Reopen

Bug Status


New: Once user enters a new bug in tracking tool, tool automatically assigns the statuscalled NEW. It means just entered or not reviewed by assignee.Open: When status is labeled “OPEN’, it means it has been reviewed and validated.Reviewed: Once assignee Reviews the Bug, Status gets changed to Reviewed.Fixed: After bug gets fixed and is compiled, Status changes to Fixed.Test: After compilation, Fixed gets assigned back to testing team to test. The Statuschanges to “Test”. It means it is ready for the test.Passed: Once assigned tester executes the fixed Bug and if it gets passed, the Status willbe changed to “Passed”. It means that the defect can be closed.Closed: When the Bug pass the test, then either the assigned tester or an Authorizedperson (either lead or manager) will close that bug by changing the status to “Closed”.Failed: If Bug doesn’t pass, means error remains the same as entered then Statuschanges to Failed.Reopen: Since this defect was fixed and tested against in new build or Releaseenvironment, it will be re-entered as “Reopen” status.

Bug Status


The following table lists the fields that must be completed when recording Bugs and providesnotes to assist the end-user on the meaning of the content within the specific field.

Bug Fields and Values

Field Type Notes

*Summary Text Brief one-line description of the submitted Bug

*Assigned To Name Name of the Responsible Developer

*Status Drop down list Status of Bug like; New, Open, Reviewed, etc.,

-Resolved by Name Default to the System

*Resolved Reason Drop down list Reason for the Bug Fix

*Resolved Date Date Bug fix date

*Closed by Name Name of the person who closed the bug. (Team Lead)

*Functional Area Drop down list The category of the Bug as it relates to the application

*Status Change Date Date Date, when Bug status was changed.

*Created by Name of the person of Entered the Bug

Defaults to your Computer

*Created Date Date Defaulted with current date

*Closed Date Date Bug closed date

*Priority Drop down list Depending on the Bug and the impact/risk to the business that the Bug poses

*Severity Drop down list Depending on the Bug and the impact/risk to the Application that the Bug poses

*Found in Version Drop down list Actual application under test version

Fixed In Version Drop down list Bug Fixed version number

*Detail Description Text Enter the details of the test step that the Bug was detected

*Step to Reproducible Text Enter the Test Steps to Reproduce the Bug if entering bug manually.


The user should include as much information as possible to allowthe Bug to be diagnosed, and re-mediated where appropriate,including:

Name of test case and test step Summary of the Bug – typically a one-line description of the Bug Screen shots Data used Test step that Bug was raised Assigned to Modified or changed by Project Status

Detail Information:


Bug Reports will be generated to measure Traceabilityon following basis:

By Requirement Coverage,By Test Script Execution Coverage,By Number of Bugs found,By Priority of the Bug(s), Etc.’

Customized reports can be created as per the need ofthe Management or team.

Bug Reports


As Bugs are updated into MTM, updatemessages should be sent to all appropriatestakeholders within testing and applicationdevelopment groups. The appropriate Teammember will compare the Bug updateinformation in MTM with the Bug informationThis Bug process should be performed on aregularly scheduled basis.

Disposition of Bugs


Thank you

mtm test management system

Documents