Description:

This page intentionally left blank AGILE TESTING: HOW TO SUCCEED IN AN EXTREME TESTING ENVIRONMENT In an IT world with differently sized projects, different applications, differently skilled practitioners, and onsite, offsite, and offshore development teams, it is impossible for there to be a one-size-fits-all agile development and testing approach. This book provides practical guidance for professionals, practitioners, and researchers faced with creating and rolling out their own agile testing processes. In addition to descriptions of prominent agile methods, the book provides twenty real-world case studies of practitioners using agile methods and draws upon their experiences to populate your own agile method; whether yours is a small, medium, large, offsite, or even offshore project, this book provides personalized guidance on the agile best practices from which to choose to create your own effective and efficient agile method. John Watkins has more than thirty years of experience in the field of software development, with some twenty-five years in the field of software testing. During his career, John has been involved at all levels and phases of testing and has provided high-level test process consultancy, training, and mentoring to numerous blue chip companies. He is both a Chartered IT Professional and a Fellow of the British Computer Society, where he is an active member of the Specialist Group in Software Testing (SIGiST), previously serving on committees of the Intellect Testing Group (representing the U.K. technology industry) and the SmallTalk User Group. He is author of Testing IT: An Off-the-Shelf Software Testing Process (Cambridge University Press, 2001) and currently works for IBM’s software group. AGILE TESTING How to Succeed in an Extreme Testing Environment JOHN WATKINS CAMBRIDGE UNIVERSITY PRESS Cambridge, New York, Melbourne, Madrid, Cape Town, Singapore, São Paulo, Delhi, Dubai, Tokyo Published in the United States of America by Cambridge University Press, New York www.cambridge.org Information on this title: www.cambridge.org 9780521191814 © John Watkins 2009 This publication is in copyright. Subject to statutory exception and to the provision of relevant collective licensing agreements, no reproduction of any part may take place without the written permission of Cambridge University Press. First published in print format 2009 ISBN-13: 978-0-511-59546-2 ISBN-13: 978-0-521-19181-4 ISBN-13: 978-0-521-72687-0 eBook (EBL) Hardback Paperback Cambridge University Press has no responsibility for the persistence or accuracy of URLs for external or third-party internet websites referred to in this publication, and does not guarantee that any content on such websites is, or will remain, accurate or appropriate. “To my Father, My Methodical Role-Model” Contents Foreword by Bob Bartlett Acknowledgments 1 Introduction 1.1 Why Agile? 1.2 Suggestions on How to Read This Book PART 1 REVIEW OF OLD-SCHOOL AND AGILE APPROACHES 2 Old-School Development and Testing 2.1 Introduction 2.2 So, What Is Process? 2.3 Waterfall 2.4 Spiral 2.5 Iterative 2.6 Traditional Elements of Test Process 2.7 Summary 3 Agile Development and Testing 3.1 Introduction 3.2 Rapid Application Development 3.3 Extreme Programming 3.4 The Dynamic Systems Development Method 3.5 Scrum 3.6 Other Agile Methods 3.7 Summary PART 2 EVERYONE IS DIFFERENT: AGILE CASE STUDIES 4 From Waterfall to Evolutionary Development and Test Tom Gilb and Trond Johansen 5 How to Test a System That Is Never Finished Nick Sewell 6 Implementing an Agile Testing Approach Graham Thomas 7 Agile Testing in a Remote or Virtual Desktop Environment Michael G. Norman 8 Testing a Derivatives Trading System in an Uncooperative Environment Nick Denning 9 A Mixed Approach to System Development and Testing: Parallel Agile and Waterfall Approach Streams within a Single Project Geoff Thompson 10 Agile Migration and Testing of a Large-Scale Financial System Howard Knowles 11 Agile Testing with Mock Objects: A CAST-Based Approach Colin Cassidy 12 Agile Testing – Learning from Your Own Mistakes Martin Phillips 13 Agile: The Emperor’s New Test Plan? Stephen K. Allot 14 The Power of Continuous Integration Builds and Agile Development James Wilson 15 The Payoffs and Perils of Offshored Agile Projects Peter Kingston 16 The Basic Rules of Quality and Management Still Apply to Agile Richard Warden 17 Test-Infecting a Development Team David Evans 18 Agile Success Through Test Automation: An eXtreme Approach Jon Tilt 19 Talking, Saying, and Listening: Communication in Agile Teams Isabel Evans 20 Very-Small-Scale Agile Development and Testing of a Wiki Dass Chana 21 Agile Special Tactics: SOA Projects Greg Hodgkinson 22 The Agile Test-Driven Methodology Experiment Lucjan Stapp and Joanna Nowakowska 23 When Is a Scrum Not a Scrum? Dr Peter May PART 3 AGILE MY WAY: A PROPOSAL FOR YOUR OWN AGILE TEST PROCESS 24 Analysis of the Case Studies 24.1 Introduction 24.2 Agile Development and Testing 24.3 Agile Process and Project Management 24.4 Agile Requirements Management 24.5 Agile Communication 24.6 Agile Meetings 24.7 Agile Automation 24.8 Summary 25 My Agile Process 25.1 Introduction 25.2 Foundation Agile Best Practices 25.3 Agile Best Practices for Small-Sized Projects 25.4 Agile Best Practices for Medium-Sized Projects 25.5 Agile Best Practices for Large-Sized Projects 25.6 Agile Best Practices for Offsite and Offshore Projects 25.7 Summary 26 The Roll-out and Adoption of My Agile Process 26.1 Introduction 26.2 Roll-out and Adoption 26.3 Maintenance of Your Agile Process 26.4 Summary Appendix A: The Principles of Rapid Application Development Appendix B: The Rules and Practices of Extreme Programming Appendix C: The Principles of the Dynamic Systems Development Method Appendix D: The Practices of Scrum Appendix E: Agile Test Script Template Appendix F: Agile Test Result Record Form Template Appendix G: Agile Test Summary Report Template Appendix H: My Agile Process Checklist References Index Ключевые слова: scrum, model, continuous integration, case study, warsaw university, worked, agile testing, david evans, extreme testing, key, appendix, requirement, automation, manager, scapa technologies, phase, spike development, denition, ensure, mock object, ha, method, result, release, term, working, testing succeed, service locator, specications, developer, lessons learned, software engineer, build, agile teams, barry boehm, story ranged, practice, solution, software, tester, round-trip communications, heartbeat retrospective, testing, haste repent, remaining error, introduction, initial denition, integration, evolutionary development, ineffective ego, mock framework, automatically collected, mike beedle, modications, org chart, defect, simple, slippage, development testing, change, code, organization, left-clicked, week, process, member, phillips chapter, problem, testing environment, shippable software, analysis, test-driven development, panopticode scan, stakeholder, study, project, rapid prototyping, dsdm phases, left-click, iteration, metric, exploratory testing, agile process, instant messaging, delivery, unambiguous manner, provide, succeed, company, xp, large-scale financial, report, large, customer, sprint, design, feasibility study, white box, timely manner, case studies, speci?cations, cost, early, environment, age award, succeed extreme, initial feasibility, case, aide memoire, scrums methodology, central cog, understand, service consumer, marketing manager, development, agile project, doe, unit, tool, technique, underlying database, net, product, extreme, progress, challenge, support, burndown chart, success, required, approach, mobile phone, uncooperative environment, agile, unit test, quality, initial skepticism, cast-based approach, story, issue, delivered, cycle, communication, role, bigger picture, effort, ishikawa shbones, worst case, people, wa, jon tilt, meeting, derivatives trading, functionality, team, mock objects, test-driven approach, dynamic mock, good, north america, cooperative approach, work, greg hodgkinson, strong case, task, business, time, graham thomas, plan, agile champion, laserguided testing, application, service provider, test-rst development, risk, predictor algorithm, finally, planning, ready, chapter, dass chana, web-based interface, group, technology, user, review, frequent integration, test, day, incremental development, idea, effective, number, ?rst, martin phillips, management, adversely affect, automated, basic, technical skill, www teamtechnology, dsdm