| |
| |
| Foreword | |
| |
| |
| |
| Foreword | |
| |
| |
| |
| Preface | |
| |
| |
| Acknowledgments | |
| |
| |
| About the Authors | |
| |
| |
| |
| Introduction | |
| |
| |
| |
| What Is Agile Testing, Anyway? | |
| |
| |
| Agile Values | |
| |
| |
| What Do We Mean by "Agile Testing"? | |
| |
| |
| A Little Context for Roles and Activities on an Agile Team | |
| |
| |
| How Is Agile Testing Different? | |
| |
| |
| Whole-Team Approach | |
| |
| |
| Summary | |
| |
| |
| |
| Ten Principles for Agile Testers | |
| |
| |
| What's an Agile Tester? | |
| |
| |
| The Agile Testing Mind-Set | |
| |
| |
| Applying Agile Principles and Values | |
| |
| |
| Adding Value | |
| |
| |
| Summary | |
| |
| |
| |
| Organizational Challenges | |
| |
| |
| |
| Cultural Challenges | |
| |
| |
| Organizational Culture | |
| |
| |
| Barriers to Successful Agile Adoption by Test/QA Teams | |
| |
| |
| Introducing Change | |
| |
| |
| Management Expectations | |
| |
| |
| Change Doesn't Come Easy | |
| |
| |
| Summary | |
| |
| |
| |
| Team Logistics | |
| |
| |
| Team Structure | |
| |
| |
| Physical Logistics | |
| |
| |
| Resources | |
| |
| |
| Building a Team | |
| |
| |
| Summary | |
| |
| |
| |
| Transitioning Typical Processes | |
| |
| |
| Seeking Lightweight Processes | |
| |
| |
| Metrics | |
| |
| |
| Defect Tracking | |
| |
| |
| Test Planning | |
| |
| |
| Existing Processes and Models | |
| |
| |
| Summary | |
| |
| |
| |
| The Agile Testing Quadrants | |
| |
| |
| |
| The Purpose of Testing | |
| |
| |
| The Agile Testing Quadrants | |
| |
| |
| Knowing When a Story Is Done | |
| |
| |
| Managing Technical Debt | |
| |
| |
| Testing in Context | |
| |
| |
| Summary | |
| |
| |
| |
| Technology-Facing Tests that Support the Team | |
| |
| |
| An Agile Testing Foundation | |
| |
| |
| Why Write and Execute These Tests? | |
| |
| |
| Where Do Technology-Facing Tests Stop? | |
| |
| |
| What If the Team Doesn't Do These Tests? | |
| |
| |
| Toolkit | |
| |
| |
| Summary | |
| |
| |
| |
| Business-Facing Tests that Support the Team | |
| |
| |
| Driving Development with Business-Facing Tests | |
| |
| |
| The Requirements Quandary | |
| |
| |
| Thin Slices, Small Chunks | |
| |
| |
| How Do We Know We're Done? | |
| |
| |
| Tests Mitigate Risk | |
| |
| |
| Testability and Automation | |
| |
| |
| Summary | |
| |
| |
| |
| Toolkit for Business-Facing Tests that Support the Team | |
| |
| |
| Business-Facing Test Tool Strategy | |
| |
| |
| Tools to Elicit Examples and Requirements | |
| |
| |
| Tools for Automating Tests Based on Examples | |
| |
| |
| Strategies for Writing Tests | |
| |
| |
| Testability | |
| |
| |
| Test Management | |
| |
| |
| Summary | |
| |
| |
| |
| Business-Facing Tests that Critique the Product | |
| |
| |
| Introduction to Quadrant 3 | |
| |
| |
| Demonstrations | |
| |
| |
| Scenario Testing | |
| |
| |
| Exploratory Testing | |
| |
| |
| Usability Testing | |
| |
| |
| Behind the GUI | |
| |
| |
| Testing Documents and Documentation | |
| |
| |
| Tools to Assist with Exploratory Testing | |
| |
| |
| Summary | |
| |
| |
| |
| Critiquing the Product Using Technology-Facing Tests | |
| |
| |
| Introduction to Quadrant 4 | |
| |
| |
| Who Does It? | |
| |
| |
| When Do You Do It? | |
| |
| |
| "ility" | |
| |
| |
| Testing | |
| |
| |
| Performance, Load, Stress, and Scalability Testing | |
| |
| |
| Summary | |
| |
| |
| |
| Summary of Testing Quadrants | |
| |
| |
| Review of the Testing Quadrants | |
| |
| |
| A System Test Example | |
| |
| |
| Tests Driving Development | |
| |
| |
| Automation | |
| |
| |
| Critiquing the Product with Business-Facing Tests | |
| |
| |
| Documentation | |
| |
| |
| Using the Agile Testing Quadrants | |
| |
| |
| Summary | |
| |
| |
| |
| Automation | |
| |
| |
| |
| Why We Want to Automate Tests and What Holds Us Back | |
| |
| |
| Why Automate? | |
| |
| |
| Barriers to Automation-Things that Get in the Way | |
| |
| |
| Can We Overcome These Barriers? | |
| |
| |
| Summary | |
| |
| |
| |
| An Agile Test Automation Strategy | |
| |
| |
| An Agile Approach to Test Automation | |
| |
| |
| What Can We Automate? | |
| |
| |
| What Shouldn't We Automate? | |
| |
| |
| What Might Be Hard to Automate? | |
| |
| |
| Developing an Automation Strategy-Where Do We Start? | |
| |
| |
| Applying Agile Principles to Test Automation | |
| |
| |
| Supplying Data for Tests | |
| |
| |
| Evaluating Automation Tools | |
| |
| |
| Implementing Automation | |
| |
| |
| Managing Automated Tests | |
| |
| |
| Go Get Started | |
| |
| |
| Summary | |
| |
| |
| |
| An Iteration in the Life of a Tester | |
| |
| |
| |
| Tester Activities in Release or Theme Planning | |
| |
| |
| The Purpose of Release Planning | |
| |
| |
| Sizing | |
| |
| |
| Prioritizing | |
| |
| |
| What's in Scope? | |
| |
| |
| Test Planning | |
| |
| |
| Test Plan Alternatives | |
| |
| |
| Preparing for Visibility | |
| |
| |
| Summary | |
| |
| |
| |
| Hit the Ground Running | |
| |
| |
| Be Proactive | |
| |
| |
| Advance Clarity | |
| |
| |
| Examples | |
| |
| |
| Test Strategies | |
| |
| |
| Prioritize Defects | |
| |
| |
| Resources | |
| |
| |
| Summary | |
| |
| |
| |
| Iteration Kickoff | |
| |
| |
| Iteration Planning | |
| |
| |
| Testable Stories | |
| |
| |
| Collaborate with Customers | |
| |
| |
| High-Level Tests and Examples | |
| |
| |
| Summary | |
| |
| |
| |
| Coding and Testing | |
| |
| |
| Driving Development | |
| |
| |
| Tests that Critique the Product | |
| |
| |
| Collaborate with Programmers | |
| |
| |
| Talk to Customers | |
| |
| |
| Completing Testing Tasks | |
| |
| |
| Dealing with Bugs | |
| |
| |
| It's All about Choices | |
| |
| |
| Facilitate Communication | |
| |
| |
| Regression Tests | |
| |
| |
| Resources | |
| |
| |
| Iteration Metrics | |
| |
| |
| Summary | |
| |
| |
| |
| Wrap Up the Iteration | |
| |
| |
| Iteration Demo | |
| |
| |
| Retrospectives | |
| |
| |
| Celebrate Successes | |
| |
| |
| Summary | |
| |
| |
| |
| Successful Delivery | |
| |
| |
| What Makes a Product? | |
| |
| |
| Planning Enough Time for Testing | |
| |
| |
| The End Game | |
| |
| |
| Customer Testing | |
| |
| |
| Post-Development Testing Cycles | |
| |
| |
| Deliverables | |
| |
| |
| Releasing the Product | |
| |
| |
| Customer Expectations | |
| |
| |
| Summary | |
| |
| |
| |
| Summary | |
| |
| |
| |
| Key Success Factorso481 | |
| |
| |
| |
| Use the Whole-Team Approach | |
| |
| |
| |
| Adopt an Agile Testing Mind-Set | |
| |
| |
| |
| Automate Regression Testing | |
| |
| |
| |
| Provide and Obtain Feedback | |
| |
| |
| |
| Build a Foundation of Core Practices | |
| |
| |
| |
| Collaborate with Customers | |
| |
| |
| |
| Look at the Big Picture | |
| |
| |
| Summary | |
| |
| |
| Glossary | |
| |
| |
| Bibliography | |
| |
| |
| Index | |