0% found this document useful (0 votes)
83 views

Testing

The traceability matrix document provides guidelines for maintaining a traceability matrix. It defines the various columns that make up the matrix like project name, module name, test script ID, test script description, expected result, actual result etc. It also provides examples for each column to help understand what type of information needs to be captured in those columns. The traceability matrix helps track requirements, test cases and defects to ensure completeness and consistency throughout the testing life cycle.

Uploaded by

api-3806986
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
83 views

Testing

The traceability matrix document provides guidelines for maintaining a traceability matrix. It defines the various columns that make up the matrix like project name, module name, test script ID, test script description, expected result, actual result etc. It also provides examples for each column to help understand what type of information needs to be captured in those columns. The traceability matrix helps track requirements, test cases and defects to ensure completeness and consistency throughout the testing life cycle.

Uploaded by

api-3806986
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 5

Traceability Matrix

Project Name :
Module Name :
Prepared By :
Reviewed By :

Reference Description Test Condition Id Test Case Id


Test Script
Project Name :
Module Name :
Prepared By :
Reviewed By :
Version No. :
Change Management Description :

Test Script ID Test Script Description Step Step Description Expected Result Actual Result Test Type Defect Id
Number
Check whether a Facility 1 Log into the application by giving the URL - The application with
Administrator is allowed to 'http://132.132.64.115/facilitylink.aspx' Title '' should be
URS2.2.1.1_1_1 create user accounts displayed
Enter a valid User Name and Password The Facility Link Home
User Name - Page should be
Password - displayed
Click 'Login' button
Click on 'User Maintenance' tab
Guidelines
S.No Column Name Description Example S.No Column Description Example
Name
1 Project Name The name of the project CCBN 1 Project Name The name of CCBN
the project
2 Module Name The name of the module Broadcast Booth 2 Module Name The name of Broadcast
the module Booth
3 Prepared By The name of the author Tom 3 Prepared By The name of Tom
the author
4 Reviewed By The name of the Jerry 4 Reviewed By The name of Jerry
reviewer the reviewer
5 Version No. The version of the 1.0, 2.0 etc.. 5 Version No. The version of 1.0, 2.0 etc..
document the document

6 Change Management The changes made in Changed the name of the field 'Customer Id' to 6 Change The changes Changed the
Description every version of the 'Customer Name' for Test Condition FS-1.0_1 Management made in every name of the
document since the draft Description version of the field
version document 'Customer Id'
since the draft to 'Customer
version Name' for
Test
Condition
FS-1.0_1

7 Test Script ID Unique script id FS-1.0-1_1, BR-1.0_1_1 etc… 7 Test Script ID Unique script FS-1.0-1_1,
id BR-1.0_1_1
etc…
8 Test Script Description The desription of the Check whether the system accepts blanks in the 8 Test Script The desription Check
test case that covers the 'Customer Name' field Description of the test whether the
condition tested case that system
covers the accepts
condition blanks in the
tested 'Customer
Name' field
9 Step Number Unique Step number 1, 2, 3 etc 9 Step Number Unique Step 1, 2, 3 etc
number
10 Step Description The steps involved to Log into the application by entering a valid user 10 Step Description The steps Log into the
execute a test case name and password involved to application
execute a test
by entering a
case valid user
name and
password
11 Expected Result The result expected by The user should be allowed to log into the 11 Expected Result The result The user
performing an action application successfully expected by should be
performing an allowed to
action log into the
application
successfully
12 Actual Result The actual outcome of The system displays an error message 12 Actual Result The actual The system
the action performed outcome of displays an
the action error
performed message
13 Test Type The Type of test carried Positive or Negative 13 Test Type The Type of Positive or
out or covered in a test test carried Negative
script out or covered
in a test script

14 Defect ID The associated defect in 001, 002 etc… 14 Defect ID The 001, 002
case a script fails associated etc…
defect in case
a script fails

Naming Naming
Convention to be Convention
followed to be
followed
File Name - <Project File Name -
Name_Module <Project
Name_Script Number> Name_Module
Name_Script
Number>

Work Sheet Name Work Sheet


<Module Name> Name
<Module
Name>

You might also like