Posts Tagged ‘cem kaner’
Review of properties in Kaner’s What is a Good Test Case? Rikard Edgren 5 Comments
One of Cem Kaner’s many classic writings is “What is a Good Test Case?” It is a very good article, well-spent time for anyone involved in software testing. But when writing about test ideas, I started to realize that the list of properties for good test cases isn’t perfect, for me. So it’s time for [...]
Exploratory Testing is not a test technique Henrik Emilsson 7 Comments
Rage against the machine Henrik Emilsson 5 Comments
As a user of Facebook I feel really helpless when nothing works as it should (as was the case with the latest GUI-update). Posts were stochastically shown in the feed and a lot of errors occurred in various situations. A lot (all?) of my friends on Facebook experienced the same problems. When there are lots [...]
Kaner’s Gold Mine Martin Jansson 2 Comments
Multidimensional Subjectivity in Software Testing Henrik Emilsson 6 Comments
I use Jerry Weinberg’s definition of quality: “Quality is value to some person”; and I use Cem Kaner’s extension to the definition so that it becomes “Quality is value to some person (that matters)”… I.e. quality is inherently subjective. And there are a lot of persons that are affected by software that we produce… With this in [...]
I am secretly in love with Cem Kaner Henrik Emilsson 3 Comments
Well, “secretly” as in that he does not know that I am in love with him… Yet! If you haven’t discovered the amazing Cem Kaner yet, I can give you the following advices and hoping that you too might fall in love some day: Visit kaner.com publications and read ANY article from his large publication-section. Buy [...]
Decisions around the product release – part 3 Martin Jansson 2 Comments
What is essence of the discussion on release team/showstopper meetings? I am assuming that there is a meeting. I’ve been to many different kinds of showstopper meetings and most companies handle them differently. One important item on the agenda for the meeting is usually the bugs that are found late in the project, thus at [...]