Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?"
Two of the industry's most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In 'Agile Testing', Crispin and Gregory define agile testing and illustrate the tester's role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.
Readers will come away from this book understanding
- How to get testers engaged in agile development
- Where testers and QA managers fit on an agile team
- What to look for when hiring an agile tester
- How to transition from a traditional cycle to agile development
- How to complete testing activities in short iterations
- How to use tests to successfully guide development
- How to overcome barriers to test automation
- This book is a must for agile testers, agile teams, their managers, and their customers.
"As Agile methods have entered the mainstream, we've learned a lot about how the testing discipline fits into Agile projects. Lisa and Janet give us a solid look at what to do, and what to avoid, in Agile testing." - Ron Jeffries, www.XProgramming.com
"An excellent introduction to agile and how it affects the software test community!" - Gerard Meszaros, Agile Practice Lead and Chief Test Strategist at Solution Frameworks, Inc., an agile coaching and lean software development consultancy
"In sports and music, people know the importance of practicing technique until it becomes a part of the way they do things. This book is about some of the most fundamental techniques in software development - how to build quality into code - techniques that should become second nature to every development team. The book provides both broad and in-depth coverage of how to move testing to the front of the development process, along with a liberal sprinkling of real-life examples that bring the book to life." - Mary Poppendieck, Author of Lean Software Development and Implementing Lean Software Development
"Refreshingly pragmatic. Chock-full of wisdom. Absent of dogma. This book is a gamechanger. Every software professional should read it." - Uncle Bob Martin, Object Mentor, Inc.
"With Agile Testing, Lisa and Janet have used their holistic sensibility of testing to describe a culture shift for testers and teams willing to elevate their test effectiveness. The combination of real-life project experiences and specific techniques provide an excellent way to learn and adapt to continually changing project needs." - Adam Geras, M.Sc. Developer-Tester, Ideaca Knowledge Services
"On Agile projects, everyone seems to ask, 'But, what about testing?' Is it the development team's responsibility entirely, the testing team, or a collaborative effort between developers and testers? Or, 'How much testing should we automate?' Lisa and Janet have written a book that finally answers these types of questions and more! Whether you're a tester, developer, or manager, you'll learn many great examples and stories from the real-world work experiences they've shared in this excellent book." - Paul Duvall, CTO of Stelligent and co-author of Continuous Integration: Improving Software Quality and Reducing Risk
"Finally a book for testers on Agile teams that acknowledges there is not just one right way! Agile Testing provides comprehensive coverage of the issues testers face when they move to Agile: from tools and metrics to roles and process. Illustrated with numerous stories and examples from many contributors, it gives a clear picture of what successful Agile testers are doing today." - Bret Pettichord, Chief Technical Officer of WatirCraft and Lead Developer of Watir
Geef uw waardering
Foreword by Brian Marick
About the Authors
Part 1: Introduction
1. What Is Agile Testing, Anyway?
-What Do We Mean by "Agile Testing"?
-A Little Context for Roles and Activities on an Agile Team
-How Is Agile Testing Different?
2. Ten Principles for Agile Testers
-What's an Agile Tester?
-The Agile Testing Mind-Set
-Applying Agile Principles and Values
Part 2: Organizational Challenges
3. Cultural Challenges
-Barriers to Successful Agile Adoption by Test/QA Teams
-Change Doesn't Come Easy
4. Team Logistics
-Building a Team
5. Transitioning Typical Processes
-Seeking Lightweight Processes
-Existing Processes and Models
Part 3: The Agile Testing Quadrants
6. The Purpose of Testing
-The Agile Testing Quadrants
-Knowing When a Story Is Done
-Managing Technical Debt
-Testing in Context
7. 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?
8. 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
9. 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
10. Business-Facing Tests that Critique the Product
-Introduction to Quadrant 3
-Behind the GUI
-Testing Documents and Documentation
-Tools to Assist with Exploratory Testing
11. Critiquing the Product Using Technology-Facing Tests
-Introduction to Quadrant 4
-Who Does It?
-When Do You Do It?
-Performance, Load, Stress, and Scalability Testing
12. Summary of Testing Quadrants
-Review of the Testing Quadrants
-A System Test Example
-Tests Driving Development
-Critiquing the Product with Business-Facing Tests
-Using the Agile Testing Quadrants
Part 4: Automation
13. Why We Want to Automate Tests and What Holds Us Back
-Barriers to Automation - Things that Get in the Way
-Can We Overcome These Barriers?
14. 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
-Managing Automated Tests
-Go Get Started
Part 5: An Iteration in the Life of a Tester
15. Tester Activities in Release or Theme Planning
-The Purpose of Release Planning
-What's in Scope?
-Test Plan Alternatives
-Preparing for Visibility
16. Hit the Ground Running
17. Iteration Kickoff
-Collaborate with Customers
-High-Level Tests and Examples
18. Coding and Testing
-Tests that Critique the Product
-Collaborate with Programmers
-Talk to Customers
-Completing Testing Tasks
-Dealing with Bugs
-It's All about Choices
19. Wrap Up the Iteration
20. Successful Delivery
-What Makes a Product?
-Planning Enough Time for Testing
-The End Game
-Post-Development Testing Cycles
-Releasing the Product
Part 6: Summary
21. Key Success Factors
-Success Factor 1: Use the Whole-Team Approach
-Success Factor 2: Adopt an Agile Testing Mind-Set
-Success Factor 3: Automate Regression Testing
-Success Factor 4: Provide and Obtain Feedback
-Success Factor 5: Build a Foundation of Core Practices
-Success Factor 6: Collaborate with Customers
-Success Factor 7: Look at the Big Picture
Managementboek Top 100
- Algemeen management
- Coaching en trainen
- Communicatie en media
- Financieel management
- Inkoop en logistiek
- Internet en social media
- IT-management / ICT
- Personal finance
- Persoonlijke effectiviteit
- Reclame en verkoop
- Strategisch management
- Werk en loopbaan