tailieunhanh - Acceptance Testing Copyright 2012 Gary Mohan

Who Is This For? This is aimed at end users who need to acceptance test a system. No prior knowledge of testing is assumed and this book has deliberately been kept as concise as possible. What Does It Cover? This book covers a simple testing approach, based on techniques that have been in use for decades. It describes how to write a test script and how to design test data intended to test against your acceptance criteria. Why Bother Testing? If you rigorously test a system prior to accepting it into the live environment, you achieve two important objectives: • • It has been verified. | Acceptance Testing Copyright 2012 Gary Mohan This book can be downloaded for free in PDF format at http Introduction Who Is This For This is aimed at end users who need to acceptance test a system. No prior knowledge of testing is assumed and this book has deliberately been kept as concise as possible. What Does It Cover This book covers a simple testing approach based on techniques that have been in use for decades. It describes how to write a test script and how to design test data intended to test against your acceptance criteria. Why Bother Testing If you rigorously test a system prior to accepting it into the live environment you achieve two important objectives It has been verified that the system works as specified. Problems with the way the system was specified are more likely to have been identified preventing the system from going live prior to it being genuinely ready. 2 Definitions Prior to discussing how to test a system it is important to define some terms Acceptance Criteria The agreed list of criteria under which the system is deemed acceptable. Typically this will be an agreement that the system performs the functions described in a series of functional specification documents. Branching An approach for storing computer software source code that allows multiple versions of a system to be worked on simultaneously. This matters in acceptance testing as a particular version will only contain functionality specific to that version. Bug Report This is a report raised when documenting that the system is not working to specification. Typically this is covered under the existing project budget. Change Request This is a request to change the behavior of the system addressing the fact that although the system is working to specification the specification itself needs to change. Typically this requires new budget. Functional Specification The body of documentation that specifies .