Microsoft   |   patterns & practices   |   Developer Network   |   Enterprise Library   |   Acceptance Testing Guide   |   Personal Site

News: Acceptance Test Engineering Guidance BETA1 - Grigori Melnik: Thoughts on Agile Software Engineering and Beyond - Site Home - MSDN Blogs

News: Acceptance Test Engineering Guidance BETA1

News: Acceptance Test Engineering Guidance BETA1

  • Comments 2

ATE_small

I am pleased to announce the release of the Acceptance Test Engineering guide BETA1. You can download it from http://codeplex.com/TestingGuidance

Common Scenarios Addressed:

  • 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

Contents at a Glance:

PART I – THINKING MODELS: an overview of acceptance testing and explains several models that are useful in conceptual thinking about acceptance testing. It also includes items that are necessary for planning acceptance testing. This part is intended to be read from beginning to end.

PART II – THUMBNAILS: a thumbnail is a short overview of a practice that explains what it is, when you may want to use it, the risks that it mitigates, and an overview of how to perform the practice. Thumbnails also include a list of references to papers, books, and other resources that provide more complete descriptions of the practice in question. The main purpose of a thumbnail is to describe a topic well enough to provide an overview, serve as a mental reminder for someone who has used the practice on how to do it, and give someone unfamiliar with the practice enough information about the practice and its applicability to determine if they want to learn more about it. This part is intended to be used as a reference; most readers will not read it from beginning to end.

PART III – SAMPLES: a collection of sample artifacts generated by applying different practices in a fictional real-world situation for Global Bank. These artifacts are embedded in a series of case studies of what the Global Bank team may have produced while building the application. The case studies provide some context to the individual artifacts. They also provide cross-references to the practices described in Part II. The artifacts are intended to be used as way to learn more about how to perform a practice; they can also be used as templates for your own artifacts.

Webcast

Gerard, Jon and I did a webcast talking about the concepts and the way we are writing this guidance.

Feedback

Your  feedback is invited. Please post it under Discussions on Codeplex. Also, if you have an interesting experience with acceptance testing that you’d like to share and perhaps be profiled in our guide as a case study, we’d like to hear about it.

 

Comments
Page 1 of 1 (2 items)
Leave a Comment
  • Please add 7 and 1 and type the answer here:
  • Post