Home > Store

Testing Extreme Programming

Register your product to gain access to bonus material or receive a coupon.

Testing Extreme Programming

Book

  • Sorry, this book is no longer in print.
Not for Sale

Description

  • Copyright 2003
  • Dimensions: 7-3/8" x 9-1/4"
  • Pages: 336
  • Edition: 1st
  • Book
  • ISBN-10: 0-321-11355-1
  • ISBN-13: 978-0-321-11355-9

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.

Sample Content

Online Sample Chapter

Why XP Teams Need Testers

Downloadable Sample Chapter

Click below for Sample Chapter(s) related to this title:
Sample Chapter 2

Table of Contents

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

This is a book about being a tester on an Extreme Programming (XP) team. It plugs a gap in the currently available XP materials by defining how an XP tester can contribute to the project, including what testers should do, when they should do it, and how they should do it. We are writing it because we think that XP is a better way to develop software and should be used by more teams. We believe that an acknowledged place in XP teams for testing and quality assurance will help bring that about.

Our goals in this book are to:

  1. Convince current XP practitioners that there is a valid role for a tester on the team
  2. Convince testing and quality assurance professionals that XP offers solutions to some of their worst problems
  3. Convince both groups that the testers are needed just as much as in an XP project as in a traditional development project
  4. Provide enough detail and practical example to allow you to either perform the XP tester role yourself or work productively with a tester on your team, whether you are an XP newbie or veteran, tester, programmer, guide, customer, or manager

We hope that if you are not currently using XP, that you can influence your own organization to try it. Even if your team uses some other process for software development, we think you can apply "extreme testing" practices to add value.

Because not everyone will be familiar with XP, we provide an overview of the basic concepts in the introduction, and describe a few aspects in more detail as necessary throughout the text. But this will be a bare-bones summary, at best, and there are several excellent books on the subject, as well as a wealth of information on the Web.

The book is divided into three major parts:

Part I - The XP Tester Role

This is where we define what we think the tester role is (and is not), how a project will benefit from it, what is in it for the tester, and generally why XP needs a tester role.

Part II - The XP Test Drive

Here we go through an XP project step by step and suggest what goals to shoot for, which activities to engage in, and helpful techniques to try as a tester on an XP project.

Part III - Road Hazard Survival Kit

Finally we provide some resources to help you cope when the real world doesn't conform exactly to the ideal XP project. Large projects, for instance, where an XP team is imbedded in a larger, non-XP effort, or when critical XP practices are modified or omitted.

We've tried to keep the things as practical as possible, and provided real-life examples as well as exercises for you to try it out for yourself. The exercises are built around an XP project to develop a simple web-based tracking application, and we provide portions of the application at various stages for you to practice on.

We think you will find this book helpful if you are already a member of an XP team, or if you are a testing/quality assurance professional, or if you are in any software development role and considering XP.



0321113551P06272002

Foreword

As I see it, I have two jobs to do in this foreword. The first is to persuade you that it's worth your time to keep reading this book. The second is to place the book in context: what does it say about the world of testing and about how that world is changing?

My first job is easy. The reason is that the book you're holding is both skimmable and eloquent. Stop reading this foreword. Go to Part II. Browse some chapters. Do you see tidbits you can put to immediate, practical use on an XP or agile project? That's a sign Lisa and Tip are writing from experience. Do the chapters seem to hang together into a coherent testing strategy? That's a sign they've thought about their experience. Is the tone flexible, avoiding dogmatism? That's a sign that you'll readily be able to adapt what you read to your local circumstances. These are the things that make the book worth reading. Don't believe me; check for yourself.

The second job is harder. How does this book fit in? As I write (May 2002), the world of testing seems stuck. We're all supposed to know certain fixed concepts: what the purpose of testing is, what the relationship of testers to programmers should be, what test planning means. When presented with a new project, it seems we're intended to take those concepts as givens, follow some methodology, and fill in the blanks through a process of top-down, stepwise refinement.

But that's not really what happens, at least not on good projects. The tester comes to a project equipped with a hodgepodge of resources: concepts, attitudes, habits, tools, and skills--some complementary, some contradictory. She begins by modeling her new situation after one she's experienced before. She applies her habits and skills. She keeps what works and changes what proves awkward. She fluidly adapts any of her resources to the situation. In her project, testing goes through what Andrew Pickering calls "the mangle of practice" (in his book of the same name).

All this is hidden, because it's disreputable in at least two ways. First, everything is up for grabs, including those seemingly fixed concepts we're all supposed to know. The practice of testing, when applied in specific contexts, changes the purpose of testing, the relations of people, what test planning means. There's precious little solid ground to stand on. Second, the trivial can be as important as the lofty. Knowing how to use 3 x 5 cards well may matter more than knowing test design techniques. Unthinking work habits may have more effect than reasoned decisions.

We need to make the mangle respectable. It's harmful when people feel vaguely ashamed of doing what has to be done. It's even worse when they don't do it because they think they must follow the rules to be "professional."

And that marks this book's significance beyond simply (!) helping XP testers. In it, you can see the traces of two people interactively adapting their practice of testing to a new sort of project, arriving at last at a point of stability: something that works well enough that they can gift it to others. It's an inspiring example. I mean that literally, in that I hope it inspires you to model your testing after it, run that model through the mangle of practice, and report back to us, saying, "Here. Here's what I do. Here's what I've seen. Here's what works for me. Try it."

Brian Marick
Champaign, Illinois
May 2002

Index

Click below to download the Index file related to this title:
Index

Updates

Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020