Tag Info

New answers tagged

1

Having done 23 years of performance tests including trouble shooting, correction, and rerun I can agree with testerab on long reports full of nice graphs that remained unread (and even if scanned certainly not understood). Of course if you are a paid for third party, or even expendable employee, that report might be the only way you can justify your costs ...


1

I have served as QA lead for multiple Scrum teams. Any release might have multiple teams releasing at the same time. I was responsible for the overall QA sign-off and test summary. What we provided as a summary document: What user stories were included from each group Any documented defects that were not fixed and therefore constituted a release risk ...


1

This all feels like a great waste of time, because there is a very big chance no-one will read them ever. I hear you on this one. I have wasted far too many hours of my life producing documents that nobody ever read - enough so that at one point, I devised Anna's Chocolate Bar Test. (Somewhere in the last half of the document, you state that you have ...


1

I do not know what documentation you currently has or what tools you use. So I do not know is all of the following possible for you. But maybe you found some helpful ideas. Defect Overview How many defects was created. How many defects was fixed/closed. How many defects of the ceated/fixed/closed has a low, medium or high priority. (Maybe you has more ...



Top 50 recent answers are included