I do not see myself as a member of any of the Schools of Testing, and I have ethical problems with labelling other people than yourself. However, I see the schools as a fruitful tool for enhancing your understanding of views on testing. So please join me in the following thought experiment. The following is […]
If you haven’t done it before, have a look at the Software Quality Characteristics that we published last year: TheTestEye – Software Quality Characteristics You can probably imagine ways of testing for all of these quality characteristics yourself, and you might even come up with good oracles that can assist you in the interpretation of the […]
When I wrote blog post The Complete List of Testing Inspiration, I didn’t think so much about many testing efforts being totally based on requirements and specifications. I took for granted that we know that requirements are incomplete and wrong, and that we should learn from many places. But when reading a good book such […]
Even if most of the program is set, there is still a chance for you to talk at CAST 2011. Matt Heusser and Pete Walen is running the Emerging Topics session: If you would like to speak at CAST 2011, you still have the option of proposing a twenty-minute emerging topics session. (Emerging topics are anything […]
Over the years, one has read quite some text about software testing. Some things have (from various sources and experiences) become clear for me, and I’m surprised when seeing articles/presentations that don’t acknowledge these insights. These “truths” are now and then implicitly disregarded: * Requirements don’t include all important information * Testing includes more than […]
I have had some problems with the notion of Risk-Based Testing. I mean, aren’t all testing based on risk in some sense, making the term redundant? When using risk techniques, you come up with a list of areas to investigate first or most. But what about those items that are extremely rare, but with very […]
The delegates of the first Swedish Workshop on Exploratory Testing were: Torbjörn Ryber, Simon Morley, Christin Wiedemann, Petter Mattsson, Anders Claesson, Oscar Cosmo, Johan Hoberg, Rikard Edgren, Henrik Emilsson, Martin Jansson, Ann Flismark, Henrik Andersson, Michael Albrecht, Johan Jonasson, James Bach. This write-up surely contains mistakes and important omissions, and it might be too heavy […]
I thought of this the other day when rethinking a situation that was described in the experience report from Petter Mattson on “Swedish Workshop on Exploratory Testing” (SWET1). Let’s say that you have 100 Paper Airplane builders in your team. They all follow scripted instructions on how to fold a paper in order to create […]
Let me begin by a quote from T.S. Eliot: We shall not cease from exploration, and the end of all our exploring will be to arrive where we started and know the place for the first time. One of the most important things with Exploratory Testing is that it allows for you to learn something […]
It is often said, with right, that you need to consider a lot more than the explicit requirements in order to be able to test a product well. Often a few examples are included, e.g. something about the customer needs, or the necessity of reading the code, or knowing the technology the software operates in, […]