Testing Extreme Programming
Published on 5. November 2002
Book
Paperback/Softback
336 pages
978-0-321-11355-9 (ISBN)
Description
Testing is a cornerstone within the burgeoning discipline of Extreme Programming. Much has been written about XP, but to date, no book has specifically addressed the key role that the tester plays in this lightweight methodology. This new book defines how an XP tester can optimally contribute to a project, including what testers should do, when they should do it, and how they should do it. Each teaching point is supported by practical examples, helpful suggestions, and proven techniques that will help readers improve the quality of their next project. The material is based on the authors' real-world experience making XP work within development organizations. The book also provides a unique "Road Hazard Survival Kit" with copious resources that help the tester address common pitfalls. Both testers unfamiliar with XP, and XP devotees unfamiliar with testing, will benefit greatly from this book.
More details
Persons
Lisa Crispin has more than ten years of experience testing Web applications, databases, 4GLs, middleware, and business applications. She first elbowed her way onto an XP team in July 2000. Lisa has published articles based on her XP testing experience in STQE Magazine, Novatica, and other technical journals. She has also presented technical papers and seminars on XP testing in the U.S. and Europe.
Tip House, a chief systems analyst at the OCLC Online Computer Library Center, has twenty-five years of experience in software development, testing, and quality assurance. Tip is a Certified Quality Analyst, Certified Software Quality Engineer, and trained Lead Ticket Auditor. He is the creator of numerous tools for test automation and software configuration, including the WebART tool, and is the author of numerous papers and presentations on software testing, software measurement, electronic document control/collaboration, and XP.
0321113551AB09262002
Tip House, a chief systems analyst at the OCLC Online Computer Library Center, has twenty-five years of experience in software development, testing, and quality assurance. Tip is a Certified Quality Analyst, Certified Software Quality Engineer, and trained Lead Ticket Auditor. He is the creator of numerous tools for test automation and software configuration, including the WebART tool, and is the author of numerous papers and presentations on software testing, software measurement, electronic document control/collaboration, and XP.
0321113551AB09262002
Content
Foreword.
Preface.
Acknowledgments.
I. THE XP TESTER ROLE.
1. An Overview.
Introduction.
Overview of XP.
Communication.
Simplicity.
Feedback.
Courage.
How XP Solves Testing and Quality Assurance Problems.
System and Acceptance Testing Resources Wasted on Unit- and Integration-Level Bugs.
Missing and Out-of-Date Requirements.
Huge Gaps between the System and User Expectations.
Wolves in Sheep's Clothing.
Summary.
2. Why XP Teams Need Testers.
Definition of Tester.
The Tester's Contribution, Illustrated.
Shun the Dark Side.
Summary.
3. How XP Teams Benefit from Having Testers.
Checks and Balances.
Acceptance Tests versus Unit Tests.
Navigating for XP Projects.
Summary.
4. XP Testing Values.
Communication.
Simplicity.
Feedback.
Courage.
Summary.
5. Overview of the XP Tester Role.
XP Tester's Bill of Rights.
XP Tester Activities.
Summary.
6. Quality and XP.
Defining Quality.
Setting Quality Criteria.
Who Is Responsible for Quality?
Summary.
II. TEST DRIVE THROUGH AN XP PROJECT.
7. User Stories and Release Planning.
The Tester's Role in Up-Front Activities.
Goals of Up-Front Tester Activities.
Summary.
Exercise 1.
8. Identifying Hidden Assumptions.
A Process for Finding Hidden Assumptions.
Example 1.
Summary.
Exercise 2.
Introducing the XTrack Application.
9. Defining High-Level Acceptance Tests.
Basic Acceptance Test Definitions.
Example 2.
Example 3.
Summary.
Exercise 3.
10. High-Level Acceptance Test Estimates.
Ways to Estimate Acceptance-Test Effort.
Quick-and-Dirty Approach.
Example 4.
A More Detailed Estimating Method.
Example 5.
Summary.
Exercise 4.
11. Enabling Accurate Estimates during Release Planning.
Why We Care about Estimates.
How You Can Improve Estimate Accuracy.
Summary.
Exercise 5.
12. Planning the First Iteration.
Overview of Iteration Planning.
The Tester's Role in Iteration Planning.
Thinking of All the Tasks.
Enhancing Communication.
Summary.
Exercise 6.
13. Defining and Estimating Testing and Test Infrastructure Tasks.
Identifying and Estimating Test Infrastructure Tasks.
Identifying and Estimating Functional and Acceptance Testing Tasks.
A Note on Separate Test Teams.
Example 6.
Test Infrastructure Tasks.
Acceptance Testing Tasks.
Summary.
Exercise 7.
14. Acceptance Tests and Quality.
Acceptance Test Details.
Internal and External Quality.
Summary.
Exercise 8.
15. Nailing Down the Details.
Picking the Customer's Brain (and the Programmers'!).
The Good, the Bad, and the Ugly.
Example 7.
Optional Tests.
Getting Creative.
Lights-Out Test Design.
Summary.
Exercise 9.
16. Writing Acceptance Tests.
Executable Tests.
If You Have Trouble Getting Started.
Summary.
Exercise 10.
17. Organizing Acceptance Tests.
Version Control of Acceptance Tests.
Executable Test Files.
Organizing Acceptance Tests in Spreadsheets.
Summary.
Exercise 11.
18. Test Design and Refactoring.
Establishing the Initial System State.
Tests That Leave the System State Unchanged.
Coupling between Tests.
Summary.
Exercise 12 130
19. Manual Tests.
Summary.
Exercise 13.
20. What!?!!
Manual Tests Are Unreliable.
Manual Tests Undermine the XP Testing Practice.
Preface.
Acknowledgments.
I. THE XP TESTER ROLE.
1. An Overview.
Introduction.
Overview of XP.
Communication.
Simplicity.
Feedback.
Courage.
How XP Solves Testing and Quality Assurance Problems.
System and Acceptance Testing Resources Wasted on Unit- and Integration-Level Bugs.
Missing and Out-of-Date Requirements.
Huge Gaps between the System and User Expectations.
Wolves in Sheep's Clothing.
Summary.
2. Why XP Teams Need Testers.
Definition of Tester.
The Tester's Contribution, Illustrated.
Shun the Dark Side.
Summary.
3. How XP Teams Benefit from Having Testers.
Checks and Balances.
Acceptance Tests versus Unit Tests.
Navigating for XP Projects.
Summary.
4. XP Testing Values.
Communication.
Simplicity.
Feedback.
Courage.
Summary.
5. Overview of the XP Tester Role.
XP Tester's Bill of Rights.
XP Tester Activities.
Summary.
6. Quality and XP.
Defining Quality.
Setting Quality Criteria.
Who Is Responsible for Quality?
Summary.
II. TEST DRIVE THROUGH AN XP PROJECT.
7. User Stories and Release Planning.
The Tester's Role in Up-Front Activities.
Goals of Up-Front Tester Activities.
Summary.
Exercise 1.
8. Identifying Hidden Assumptions.
A Process for Finding Hidden Assumptions.
Example 1.
Summary.
Exercise 2.
Introducing the XTrack Application.
9. Defining High-Level Acceptance Tests.
Basic Acceptance Test Definitions.
Example 2.
Example 3.
Summary.
Exercise 3.
10. High-Level Acceptance Test Estimates.
Ways to Estimate Acceptance-Test Effort.
Quick-and-Dirty Approach.
Example 4.
A More Detailed Estimating Method.
Example 5.
Summary.
Exercise 4.
11. Enabling Accurate Estimates during Release Planning.
Why We Care about Estimates.
How You Can Improve Estimate Accuracy.
Summary.
Exercise 5.
12. Planning the First Iteration.
Overview of Iteration Planning.
The Tester's Role in Iteration Planning.
Thinking of All the Tasks.
Enhancing Communication.
Summary.
Exercise 6.
13. Defining and Estimating Testing and Test Infrastructure Tasks.
Identifying and Estimating Test Infrastructure Tasks.
Identifying and Estimating Functional and Acceptance Testing Tasks.
A Note on Separate Test Teams.
Example 6.
Test Infrastructure Tasks.
Acceptance Testing Tasks.
Summary.
Exercise 7.
14. Acceptance Tests and Quality.
Acceptance Test Details.
Internal and External Quality.
Summary.
Exercise 8.
15. Nailing Down the Details.
Picking the Customer's Brain (and the Programmers'!).
The Good, the Bad, and the Ugly.
Example 7.
Optional Tests.
Getting Creative.
Lights-Out Test Design.
Summary.
Exercise 9.
16. Writing Acceptance Tests.
Executable Tests.
If You Have Trouble Getting Started.
Summary.
Exercise 10.
17. Organizing Acceptance Tests.
Version Control of Acceptance Tests.
Executable Test Files.
Organizing Acceptance Tests in Spreadsheets.
Summary.
Exercise 11.
18. Test Design and Refactoring.
Establishing the Initial System State.
Tests That Leave the System State Unchanged.
Coupling between Tests.
Summary.
Exercise 12 130
19. Manual Tests.
Summary.
Exercise 13.
20. What!?!!
Manual Tests Are Unreliable.
Manual Tests Undermine the XP Testing Practice.