The Acceptance Test Engineering Guide will provide guidance for technology stakeholders (developers, development leads, testers, test leads, architects, etc.) and business stakeholders (managers, customers, end users, etc) on the discipline of acceptance testing.
Common Scenarios
Here are the key scenarios the guide addresses:
- How to Plan for Acceptance Testing
- What Kinds of Acceptance Tests to Run
- How to Create and Run Acceptance Tests
- Defining What “Done” Means
- How to Justify Your Approach
- How to Streamline Your Acceptance Process
- Part I - Thinking About Acceptance
- Part II - Perspectives on Acceptance
- Part III - Acceptance Software
Part I - Thinking About Acceptance
Chapter 1 The Acceptance Process
Chapter 2 Decision-Making Model
Chapter 3 Project Context Model
Chapter 4 System Requirements Model
Chapter 5 Risk Model
Chapter 6 Doneness Model
Part II - Perspectives on Acceptance
Chapter 7 Business Lead’s Perspective
Chapter 8 Product Manager’s Perspective
Chapter 9 Test Manager’s Perspective
Chapter 10 Development Manager’s Perspective
Chapter 11 User Experience Specialist’s Perspective
Chapter 12 Operations Manager’s Perspective
Chapter 13 Solution Architect’s Perspective
Chapter 14 Enterprise Architect’s Perspective
Chapter 15 Legal Perspective
Part III - Acceptance Software
Chapter 16 Planning for Acceptance
Chapter 17 Assessing Software
Chapter 18 Managing the Acceptance Process
Chapter 19 Streamlining the Acceptance Process
More at Codeplex site: http://codeplex.com/TestingGuidance
No comments:
Post a Comment