A Clash of Models
Creating models of the application under test is an essential part of software testing. Usually, a tester creates more than one model and for more than one purpose. By comparing two different approaches to creating a Product Coverage Outline we discuss the reasons why the exploration of the application under test is not always the most suitable starting point for a Product Coverage Outline.
In our opinion some testers have a predisposition toward learning and understanding the application. They habitually apply a standard tool (a mind map) and a standard structure (the SFDIPOT tree structure) without questioning the feasibility of that approach. We compare the outcomes of an exercise in which two teams participated and found that surprisingly different results were derived from the same mission, using the same heuristic on the same application.