So you read my Edible versions post and want to get the good stuff on how to make it happen in your organization. Well, to be honest, its not that difficult once all the parties sit together, talk about their expectations and design the protocols between the groups. See my earlier post for some general pointers.Having said that - Maybe I CAN provide some tips that I saw working in the past:Ensure all content in a delivery is tracked as [...]
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 the version, what to expect of it?Now all of you DEV people - think about the times where you installed 3rd party products/updates which caused you the same [...]
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 other requirements as well) how does one go about checking whether the product quality is indeed high?Those who reached a fairly intermediate level of QA understanding would [...]
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 Customer ImpactThe idea here is to only have a single priority/severity field. The reporter assigns it according to his understanding of the customer impact (severity, likelihood, [...]
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 bug? To be clear, we are talking a bug report of course. The quality here refers to the accuracy of the scenario, describing exactly what is [...]
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 organizations are running under the same roof, there must be some joint interest/goal, but the challenge is to identify the expectations of each group in order [...]
As I previously hinted in "Building a test case management solution", I'm personally of the opinion that the holy grail in test case management is in finding the way to manage tests via an issue tracker database.In the time since that post I didn't find much information about this, and didn't see tools taking this approach.Therefore, it was great to stumble upon Agile06 - François Beauregard - GreenPepper Software - a podcast discussion where I learned about greenpepper, a test [...]