Posts Tagged ‘testing explained’

Questions that testing constantly help answering January 12, 2010 1 Comment

I have been thinking about qualitative research lately, and wondered what the question(s) would look like if testing was seen as a research project.
The testing effort has many positive effects, but one common and important is to provide information about the product, so a good release decision can be made. We cannot prove that the [...]

In search of the potato… December 10, 2009 2 Comments

When preparing for EuroSTAR 2009 presentation I drew a picture to try to explain that you need to test a lot more than the requirements, but we don’t have to (and can’t) test everything and the qualitative dilemma is to look for and find the important bugs in the product.
Per K. instantly commented that it [...]

What’s so special about software testing? September 8, 2009 4 Comments

There are some things about software testing that are special, but not unique:
* you are never done, and there is always something to do
* you have to be creative very often
* you are dependent on new, different and conflicting technologies, users, objectives
It’s not easy to be a tester, thank God for that!
And there are some [...]

Michael Bolton on Testing vs. Checking August 31, 2009 2 Comments

I just want to promote a really good blog post written by Michael Bolton where he describes the difference between Testing and Checking:
http://www.developsense.com/2009/08/testing-vs-checking.html
I wish that many managers, testers and developers read this post…
Cheers,
Henrik

I am secretly in love with Cem Kaner June 15, 2009 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 http://www.kaner.com/articles.html and read ANY article from his large publication-section.
Buy and read any of [...]

Multi-Dimensional Software Testing March 11, 2009 4 Comments

Thare are many ways to look at the problem of testing software, and it is rarely wise to use only one; that’s why there are so many mnemonics, e.g. SFDPOT, CRUSSPIC STMPL, HICCUPPS, FCC CUTS VIDS (http://www.satisfice.com/tools/satisfice-tsm-4p.pdf, http://www.developsense.com/articles/Testing%20Without%20A%20Map.pdf, http://www.testingreflections.com/node/view/2823)
Here are some questions for your confusion:
1) What?
a) The functionality, what the software does from A to [...]

How do you go about testing? May 21, 2008 1 Comment

A project manager, that had no knowledge about testing whatsoever, asked me how he should go about testing? The question was vague since he did not know where to start. I wrote him a quick email listing a few things to consider:

Create a list of all use cases. For each use case consider possible errors. [...]