tag:blogger.com,1999:blog-85759660054194216002024-11-01T01:07:50.315-07:00Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8575966005419421600.post-49175277584335624302010-05-21T13:13:00.000-07:002010-05-23T14:10:06.253-07:00

As a Test Engineer or, more specifically, as a member of Quality Control team, I was never so frustrated when I look at the defects and the information provided. But as time passed, I realized that a lot of the useful information that was found on the defect management system couldn't be reported using metrics. Following were the hidden messages that were important to decipher. Defect

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-8575966005419421600.post-55266195368575095452010-05-12T09:50:00.000-07:002010-05-12T09:59:12.785-07:00

I heard our managers and client very often talking about Traceability of requirements with the Test Cases/Scenarios but I found that it is in discussion only and very few projects actually follow Requirement Traceability. We try to prove many a times to management/client by using other ways of showing traceability of requirements, so let's take a tour - What is Traceability Matrix? Requirement

Unknownnoreply@blogger.com2