Using customer wish as test plan
Goal: Learn why and how to describe the customer wish in the form of a test plan and test design, and as such make it easier to test automation.
A past ideal of development was a staged one, where each phase would finish before the next started, just like a waterfall, with water flowing from one level to the other. Moving from the customer wish through requirements gathering to analysis, to design, to coding, to testing, and finally operation and maintenance. Each phase would have its deadlines, and documented deliverables are handed off to the next phase. One of the major drawbacks of this system is its lack of responsiveness to changing insights, resulting in changing requirements. Another is the significant overhead of documents produced.
In the recent decade or two, agile methodologies have become a general practice for tackling these drawbacks. And thus, introducing with a test plan an extra document – and with it a test design –...
