Anonymous

• Feb 8th, 2006

 

Re:how is traceability of bug follow?

 

The traceability of bug can we followed in so many ways.

• *Mapping the Functional requirements scenarios (FS Doc) - test cases(ID) -- Failed test cases (Bugs)
• Mapping between requirements (RS Doc) - test case (ID) - Failed Test Case
• Maping between Test plan (TP Doc)- test case (ID) - Failed Test case
• mapping between business requirements (BR Doc) - test Case (ID) - Failed Test case
• Mapping between High Level Design (Design doc) - Test Case (ID) - Failed test case.

Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and  test cases.

Typically, in test situations, traceability matrices are used to trace requirements to test cases in order to ensure that there are test cases for all the requirements. Some easily aviailable commercial tools like Rational Suite Enterprise, will help testing engineer/ test lead to  trace requirements and then to trace from the use cases and/or requirements to test cases.

Of course, usually many types of traceability matrices may be created a just simple concept of REVERSE ENGINEERING. For example, you may  trace Bug--> identify that test cases-->use cases and vice versa. The default term likely applies to tracing requirements to test cases though.

jnanjit

 Profile Answers by jnanjit 

• May 13th, 2006

 

Traceability of bug can be followed by Bug tracking tools also.To check is there any bug in the open status or not it can be varyfied by the bug tracking tools if and only if your bug tracking tool has the provision for the test case ID where the bug is found.In the report generation for the bug, if there is some field say "Test Case ID" then it can be a method for trace a bug.correct me if i am wrong

Sujatars

 Profile Answers by Sujatars 

• Jun 21st, 2007

 

The traceability of bug can we followed in so many ways.

• *Mapping the Functional requirements scenarios (FS Doc) - test cases(ID) -- Failed test cases (Bugs)
• Mapping between requirements (RS Doc) - test case (ID) - Failed Test Case
• Maping between Test plan (TP Doc)- test case (ID) - Failed Test case
• mapping between business requirements (BR Doc) - test Case (ID) - Failed Test case
• Mapping between High Level Design (Design doc) - Test Case (ID) - Failed test case.

Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and  test cases.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 20th, 2009

 

We can trace the bugs using above said ways, but most of the cases we followed the test case document ie just leave all the cases which are passed, logged the defects which are failed.

prathyusha

• Nov 2nd, 2011

 

It is adoc ensure that each and every low level req holds a minimum of at least one single test case

The flow of Traceability Matrix

s.no->Module name->high level req->low level req->req id->date of creation->revised by->test cases->author name->attachments->test scripts->defects