- STAFF PICKS
- GIFTS + GIFT CARDS
- SELL BOOKS
- FIND A STORE
New Trade Paper
Currently out of stock.
available for shipping or prepaid pickup only
More copies of this ISBN
Testing Extreme Programming (XP Series)by Lisa Crispin
Synopses & Reviews
The rapid rise in popularity of Extreme Programming (XP) has put the practice of software testing squarely in the spotlight of application development. At one time, testing was a neglected practice, a highly specialized activity that came as an afterthought as complex, code-intensive projects were rushed to completion. But in today's world of escalating quality expectations, testing is a key component of the development process.
XP accelerates testing by demanding its complete integration with development. This in turn has pushed software professionals to rethink their traditional attitudes toward testing. XP asks the entire development team to embrace testing. In fact, testing is so critical to the XP methodology that programmers are required to write automated tests before they begin coding. Until now, however, there has been a distinct lack of instruction specific to testing and how it relates to XP.
Testing Extreme Programming is a practical tutorial that gives software builders a lucid understanding of this important aspect of development. This book demonstrates how testing is central to the XP project, clearly spelling out what testing should be done and when and how it should be performed. The authors teach by example, and readers will be able to improve their knowledge of the testing process by completing the book's exercises.
In addition, this book:
Many software engineers have dismissed XP as a throw-out-the-rulebook, anything-goes technique. It isn't. As this book shows, XP is a deliberate and disciplined approach to software development. Many software engineers have reaped the benefits of this agile methodology because its emphasis on testing eliminates much of the risk inherent in software projects. XP helps developers produce software on time, under budget, and at a higher quality level. But you can't XP if you don't test. With this book as a guide, you will learn to embrace testing. A sound testing program is the engine that drives an XP project.
Book News Annotation:
This practical tutorial for software builders demonstrates how testing is central to the extreme programming (XP) approach and explains what testing should be done and when and how it should be performed. It overviews the XP methodology, defines the roles of XP team members, shows how to write effective tests before coding begins, and sheds light on refactoring and how it relates to testing. A "road hazard survival kit" offers advice on challenges in testability, project tune-ups, large projects, and extreme testing without extreme programming.
Annotation c. Book News, Inc., Portland, OR (booknews.com)
Testing is a cornerstone of XP, tests are written for every piece of code before it is programmed. This workbook helps testers learn XP, and XP devotees learn testing. 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.
With this book as a guide, you will learn to embrace testing. A sound testing program is the engine that drives an XP project.
About the Author
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.
Table of Contents
I. THE XP TESTER ROLE.
Overview of XP.
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.
2. Why XP Teams Need Testers.
Definition of Tester.
The Tester's Contribution, Illustrated.
Shun the Dark Side.
3. How XP Teams Benefit from Having Testers.
Checks and Balances.
Acceptance Tests versus Unit Tests.
Navigating for XP Projects.
4. XP Testing Values.
5. Overview of the XP Tester Role.
XP Tester's Bill of Rights.
XP Tester Activities.
6. Quality and XP.
Setting Quality Criteria.
Who Is Responsible for Quality?
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.
8. Identifying Hidden Assumptions.
A Process for Finding Hidden Assumptions.
Introducing the XTrack Application.
9. Defining High-Level Acceptance Tests.
Basic Acceptance Test Definitions.
10. High-Level Acceptance Test Estimates.
Ways to Estimate Acceptance-Test Effort.
A More Detailed Estimating Method.
11. Enabling Accurate Estimates during Release Planning.
Why We Care about Estimates.
How You Can Improve Estimate Accuracy.
12. Planning the First Iteration.
Overview of Iteration Planning.
The Tester's Role in Iteration Planning.
Thinking of All the Tasks.
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.
Test Infrastructure Tasks.
Acceptance Testing Tasks.
14. Acceptance Tests and Quality.
Acceptance Test Details.
Internal and External Quality.
15. Nailing Down the Details.
Picking the Customer's Brain (and the Programmers'!).
The Good, the Bad, and the Ugly.
Lights-Out Test Design.
16. Writing Acceptance Tests.
If You Have Trouble Getting Started.
17. Organizing Acceptance Tests.
Version Control of Acceptance Tests.
Executable Test Files.
Organizing Acceptance Tests in Spreadsheets.
18. Test Design and Refactoring.
Establishing the Initial System State.
Tests That Leave the System State Unchanged.
Coupling between Tests.
Exercise 12 130
19. Manual Tests.
Manual Tests Are Unreliable.
Manual Tests Undermine the XP Testing Practice.
Manual Tests Are Divisive.
The Wings-Fall-Off Button.
What If You Have Manual Tests?
21. Test Automation.
22. Making Executable Tests Run.
Linking the Executable Test to an Application Test Class.
Defining the Application Test Class.
Calling the Code to be Tested.
Running the Test.
Getting Additional Tests to Run.
Combining Multiple Tests into Test Suites.
Exercise 16 156
23. Running Executable Tests through Other Interfaces.
Code Missed by Direct Calls.
Expanding Coverage of the Executable Tests.
Interfacing to a Test Tool.
Creating an Application Test-Interface Class.
Refactoring the Direct-Call Interface.
Refactoring the Application Test Class.
Creating a Tool-Specific Interface Class.
One Team's Experience with Direct-Call Test Automation.
24. Driving the System with a Test Tool.
Main WebART Script.
25. Bugs on the Windshield: Running Acceptance Tests.
How Often Do You Run Acceptance Tests?
Educating the Customer.
Road Food for Thought.
26. Looking Back for the Future.
27. Keep On Truckin': Completing the XP Road Trip.
When XP Projects End.
III. ROAD HAZARD SURVIVAL KIT.
28. Challenges in “Testability” .
Designing for Testability.
A Real-Life Example.
29. Selecting and Implementing Tools.
Other Tools Related to Quality.
Choosing an Off-the-Shelf Tool.
Experimenting with Tools.
30. Project Tune-Ups.
Accessorizing for XP.
Other Obvious Best Practices.
Additional Tester Duties.
31. Introducing XP to Your Organization: A Tester's Point of View.
Test Phases and Practices.
Introducing People to the XP Tester Role.
Helping XP Testers Succeed.
XP Testing with Blended Practices.
What If You Don't Have Enough Testers?
32. XP for Projects of Unusual Size.
Advance Planning Pays Off.
Working with Customers.
Satisfying Customer Test Documentation Requirements.
Iteration Planning and Execution for Large or Multilocation Projects.
33. Extreme Testing without Extreme Programming.
Planning and Defining Tests.
Let Worry Be Your Guide.
34. In Closing: May the Road Rise Up to Meet You.
Answers to Exercises.
What Our Readers Are Saying
Other books you might like
Computers and Internet » Software Engineering » General