Integrated Test Design and Automation: Using the Testframe Method
Authors: Hans Buwalda, Dennis Janssen, Iris Pinkster, Paul Watters
Venue:  (2001)

From the Book:No company can function without IT. Without computer programs and information systems, products cannot be made at all or remain unsold, invoices are not sent, and communications grind to a standstill. IT has developed from being a precondition into being one of a companys primary operations.This means that heavy demands are made on the systems operation. Quality-to-market is of crucial importance. Double entries in address files may be annoying, but critical incidents can occur if modern technology lets you down during company operations. Poor quality results in loss of clients and damages the companys reputation. In short, a systems failure can have dramatic consequences for the core business of a company or institution.Elaborate manual testing, to safeguard a high quality-to-market, is a time-consuming process  time that is not usually available because the time-to-market span is becoming increasingly short. Further deregulation and globalization of markets has intensified competitive pressures. Products and services must be launched as rapidly as possible. In practice, however, the development of IT systems often takes more time than expected, while the completion date is always on your tail. This is the dilemma you face. Elaborate testing takes too much time and any drastic shortening of the test path paves the way for production faults. Just consider the costs of rectifying production faults if they only surface after the development process.The authors describe a testing method that offers a solution to this dilemma. TestFrame&reg; provides a structured approach to testing thus enabling your organization to performtests rapidly, as well as thoroughly. The structured testing approach is represented in the TestFrame temple metaphor, and TestFrame phasing. This book discusses ways of putting the TestFrame model and phasing into practice. It does not aspire to be a comprehensive theoretical discussion about testing. However, it does provide a basis for performing tests in a practical way, and contains many examples that clarify key testing principles. RoadmapTesting is a complex matter. There is much to say about testing, and this book covers many different aspects. Different stakeholders, such as IT managers, test managers, test analysts, test navigators, project managers, developers, and QA officers, are interested in testing. Not every part of this book is relevant to everyone. The chapter outlining the principles behind the TestFrame method (Chapter 1) is a must read for everyone and is the basis for the other chapters. For specialized groups of readers, the following is recommended:IT managers will be interested in the place of testing in an organization, and an outline of the TestFrame approach. This information can be found in Chapters 1 and 2; it is recommended that test managers read the chapters concerning preparation of a test project (risk analysis, test strategy, writing a test plan), the chapter concerning test execution (planning of execution, error management) and, of course, the chapter specifically about test management (Chapter 6); test analysts should read the chapter Analysis (Chapter 3) where a method is presented that leads to a structured, maintainable test set. Special attention is given to selecting the right testing techniqu the job at hand. Since test analysts are greatly influenced by choices that are made during the preparation, this chapter is particularly relevant; test navigators are the testers who are concerned with automating the test. Navigation (Chapter 4) discusses test automation within TestFrame, and is a must read for them. Since these activities are directly related to some tasks that are performed during the test analysis, Chapter 3 is also recommended; project managers and developers will mainly be interested in the interfaces between development and testing. These are described in the preparation, execution and test management chapters (Chapters 2, 5 and 6); QA officers focus on the test process seeking to answer questions such as is it measurable, traceable and provable? TestFrame provides a means of achieving a structured, controlled test process with tangible products. This information is found throughout the book. However, a QA officer could begin with Chapter 1 and read other chapters when the need occurs.AcknowledgementsThe TestFrame Research Center supported the writing of this book. The Research Center is part of CMG. Its aim is to carry on developing the TestFrame method and testing as a field of expertise within CMG. This is also an appropriate place to thank several people for the enormous amount of work they have carried out. First and foremost, the authors want to thank all the people who have contributed to the book  Elvira Beekman, Bob van de Burgt, Rolf Daalder, Dirk van Dael, Erik Jansen, Maartje Kasdorp, Andr&eacute; Kok, Marc Koper, Bob Mohr, Peter den Ouden, Jan Paulusse and team Rotterd Sanders, Chris Schotanus, Anita Vocht and Michiel Vroon.No less important are the reviewers who have gone through all the material and provided useful comments. Thank you Martijn Brouns, Erik Brouwer, Steven Frisart, Edwin Hubers, Gerrit de Koning, Rik Marselis, Frank Stolker, Jon van der Strate, Kie Liang Tan, Bob Verhoeff, Jeroen Voorn, Michel Wemmenhove, Menno Wieringa and Leon Wolters. In addition, several anonymous reviewers contributions improve the book.Finally, we would, of course, like to thank our customers  they gave us the opportunity to apply and improve TestFrame in challenging test projects.