What's hot ? (and I mean really ...) - scroll down for more
1).  Code Templating - advanced usage of delegates & generics: my slides & demos are available for download! CodeProject article is also available.

2).  My series "TDD in the eyes of a simpleminded" is in progress(including code!): preface, part1, part2, Q&A 1, Manual Stub .vs. Mock Stub

3).  TDD Workshop: SeeCompass v0.1 and v0.2 are out.
# Monday, June 05, 2006
# Bug life cycle - in the eyes of a Programmer

We are working pretty tight with our QA department. Yes, we have some well-documented work procedures but some times I feel that they are too well-documented. After all, we are lazy; We want something easy to see, easy to read & easy to do.

I thought it will be better to document our relations (Development team with QA) in a simple flow diagram:
Bug life cycle - in the eyes of a programmer.ppt (55.5 KB)

update:

I've added a step: what should I (the programmer) do if I can't reproduce the bug ?
Thanks Shani.

Maybe it will help you as well.

Management
Posted by Oren Ellenbogen 
05/06/2006 01:21, Israel time UTC+03:00,     Comments [2]  |  Related posts:
Best teams work for each other
Left Brain Storming
Can you build software like House ?
Continuous Integration as Quality Reflection
Vision from an ex-software prisoner, Part 1
agile Confidence
Wednesday, June 07, 2006 12:51:09 AM (Jerusalem Standard Time, UTC+02:00)
hi,
What if the bug exists but could not reproduce by the programmer?!
your flow does not handle such case!
would you still change it to rejected?

I would like to change the status to: "bad bug report" or "couldn't track your bug"
thanks.
Shani Raba
Wednesday, June 07, 2006 11:15:24 AM (Jerusalem Standard Time, UTC+02:00)
That's a great point. I totally forgot about it.

I'll add it and upload the new ppt again.

Thanks !
Oren Ellenbogen
Comments are closed.