Print Page | Close Window

Traceability (Traceability Matrix)

Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Functional Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Functional Software Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=2820
Printed Date: 09May2024 at 1:48am


Topic: Traceability (Traceability Matrix)
Posted By: tanushree
Subject: Traceability (Traceability Matrix)
Date Posted: 15Oct2007 at 12:05am
Traceability (Traceability Matrix)
Test Cases need to be traced / mapped back to the appropriate requirement. Once all aspects of a requirement have been tested by one or more test cases then the test design activity for that requirement can be considered complete. A common misconception made during this process is that all test cases that exercise a particular requirement should be mapped to that requirement - only those test cases that are specifically created to test a requirement should be traced to that requirement. This approach gives a much more accurate picture of the application when coverage analysis is done - failure of a test case does not mean failure of all the requirements exercised (as opposed to tested by) the test case.

Test Case Execution

As in all phases of testing the appropriate set of test cases need to be executed and the results of those test cases recorded. Which test cases are to be executed should be defined within the context of the Test Plan and the current state of the application being tested. If the current state of the application does not support the testing of one or more requirements then this testing should be deferred until it does justify the expenditure of testing resources.




Print Page | Close Window