All you QA people out there – How often does your QA group “choke” on versions delivered by the development group? Are you used to “unedible” versions which just don’t taste right? How about versions which simply come as a blackbox where you have no idea what changed, therefore no idea what to do with …
How do you know your QA effort is being effective ? Based on the different stakeholders which require input from the QA a typical answer might be that Product quality is high when released to customers. Assuming that is indeed more or less what someone expects (I’d say effective QA needs to answer to some …
There are a couple of alternatives for managing severity and priority in the Issue Tracker.Although there are many resources out there on this subject (see http://del.icio.us/yyeret/priority_severity) I’ll try to consolidate them and provide my 2c on the matter, as I think its an important subject. Single-field PriorityFirst, seemingly simpler alternative, is Single-field priority – representing …
In another post in the series about QA/DEV protocols, I’ll talk about opening high quality bugs, why its important, what are the forces operating on each side of the trench here, and try to describe an approach that might improve the state of affairs a bit. First – a definition. What is a high quality …
I’m going to dedicate a couple of posts to the relationships between QA and Development (DEV) organizations. Anyone who’s ever been in either of those organizations knows that sometimes there seems to be a conflict of interest between QA and DEV, which can lead to friction between the groups and the people. Obviously when both …
