But testing a piece of software without documentation isn't something that's going to go away, regardless of how loud we, the testers, complain or shout about it. The sad reality of life is that this has happened in the past, it is still happening now and will, undoubtedly, continue to happen in the future.
Rather than discarding this undesirable task of testing without documentation as one of life's little unavoidable evils, we should learn to cope with this situation so that when we are faced with this situation again, we would at least know how to do the best job we can, rather than complaining that it makes our lives hard.
So, what do we do when we are faced with the situation of having to test an application with nothing to compare it with?
You would use Exploratory Testing to discover what the application does, and treating purely as a Black Box.
You would record the behaviour that we observed, in as much detail as possible. This means the following:
- running end-to-end scenarios of the application, on the first instance
- for each interface/dialog, trying out all controls (e.g. text boxes, check boxes, lists, drop-down boxes, radio buttons) and noting their behaviours
- Making a list of all input data type/class and how they are processed by the system and the outputs generated.
Any discrepancies identified between the system behaviour and what the user expected or what the analyst designed can then be deemed as defects.
No comments:
Post a Comment