When testing software, the very best inspiration and reality check comes from the software itself. It helps you test beyond requirements, and investigate what the software really is capable, and incapable, of. These are my best practices for exploratory testing. 1. understand what’s important – we can’t test everything, and we can’t find all bugs. […]
Some years ago I read about Soap Opera testing too hastily, and started using it at work being convinced that it meant the following: A soap opera test involves normal operations, but a large amount of them, for a long time. As in the TV shows, they go on, and on, and on, and on, […]
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, […]