Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin (En

Description: Agile Testing by Lisa Crispin, Janet Gregory Covers key issues such as values, practices, organisation, collaboration, metrics, infrastructure, documentation and tools. FORMAT Paperback LANGUAGE English CONDITION Brand New Publisher Description Two of the industrys 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 testers 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 Notes Covers key issues such as values, practices, organisation, collaboration, metrics, infrastructure, documentation and tools. Back Cover 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 testers 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 industrys 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 testers 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. Author Biography Lisa Crispin is dedicated to helping agile teams and testers discover good ways to deliver the best possible product. She specializes in showing testers and agile teams how testers can add value and how to guide development with business-facing tests. Since 2003, shes been a tester on a Scrum/XP team at ePlan Services, Inc., and frequently leads tutorials and workshops on agile testing at conferences. Lisa regularly contributes articles about agile testing to publications such as Better Software magazine, I EEE Software, and Methods and Tools. Lisa also coauthored Testing Extreme Programming (Addison-Wesley, 2002) with Tip House. Janet Gregory is the founder of DragonFire, Inc., an agile quality process consultancy and training firm. Her passion is helping teams build quality systems. Since 1998, she has worked as a coach and tester introducing agile practices into both large and small companies. Her focus is working with business users and testers to understand their role in agile projects. Janet is a frequent speaker at agile and testing software conferences, and she is a major contributor to the North American agile testing community. Table of Contents Chapter 1: What Is Agile Testing, Anyway? Chapter 2: Ten Principles for Agile Testers Chapter 3: Cultural Challenges Chapter 4: Team Logistics Chapter 5: Transitioning Typical Processes Chapter 6: The Purpose of Testing Chapter 7: Technology-Facing Tests that Support the Team Chapter 8: Business-Facing Tests that Support the Team Chapter 9: Toolkit for Business-Facing Tests that Support the Team Chapter 10: Business-Facing Tests that Critique the Product Chapter 11: Critiquing the Product Using Technology-Facing Tests Chapter 12: Summary of Testing Quadrants Chapter 13: Why We Want to Automate Tests and What Holds Us Back Chapter 14: An Agile Test Automation Strategy Chapter 15: Tester Activities in Release or Theme Planning Chapter 16: Hit the Ground Running Chapter 17: Iteration Kickoff Chapter 18: Coding and Testing Chapter 19: Wrap Up the Iteration Chapter 20: Successful Delivery Chapter 21: Key Success Factors Glossary Bibliography Index Review "As Agile methods have entered the mainstream, weve 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, "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 teams 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 youre a tester, developer, or manager, youll learn many great examples and stories from the real-world work experiences theyve 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 Long Description Te>Two of the industrys 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 testers 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. The eBook edition of Agile Testing also is available as part of a two-eBook collection, The Agile Testing Collection (9780134190624). Review Text "As Agile methods have entered the mainstream, weve 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, "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 teams 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 youre a tester, developer, or manager, youll learn many great examples and stories from the real-world work experiences theyve 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 Review Quote "As Agile methods have entered the mainstream, weve 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, "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 teams 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 youre a tester, developer, or manager, youll learn many great examples and stories from the real-world work experiences theyve 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 Feature Get past the myths of testing in agile environments - and implement agile testing the RIGHT way For everyone concerned with agile testing: developers, testers, managers, customers, and other stakeholders Covers every key issue: Values, practices, organizational and cultural challenges, collaboration, metrics, infrastructure, documentation, tools, and more By two of the worlds most experienced agile testing practitioners and consultants Introduction or Preface Preface Preface We were early adopters of Extreme Programming (XP), testing on XP teams that werent at all sure where testers or their brand of testing fit in. At the time, there wasnt much in the agile (which wasnt called agile yet) literature about acceptance testing, or how professional testers might contribute. We learned not only from our own experiences but from others in the small agile community. In 2002, Lisa co-wrote Testing Extreme Programming with Tip House, with lots of help from Janet. Since then, agile development has evolved, and the agile testing community has flourished. With so many people contributing ideas, weve learned a whole lot more about agile testing. Individually and together, weve helped teams transition to agile, helped testers learn how to contribute on agile teams, and worked with others in the agile community to explore ways that agile teams can be more successful at testing. Our experiences differ. Lisa has spent most of her time as an agile tester on stable teams working for years at a time on web applications in the retail, telephony, and financial industries. Janet has worked with software organizations developing enterprise systems in a variety of industries. These agile projects have included developing a message-handling system, an environmental-tracking system, a remote data management system (including an embedded application, with a communication network as well as the application), an oil and gas production accounting application, and applications in the airline transportation industry. She has played different roles--sometimes tester, sometimes coach--but has always worked to better integrate the testers with the rest of the team. She has been with teams from as little as six months to as long as one-and-a-half years. With these different points of view, we have learned to work together and complement each others skill sets, and we have given many presentations and tutorials together. Why We Wrote This Book Several excellent books oriented toward agile development on testing and test patterns have been published (see our bibliography). These books are generally focused on helping the developer. We decided to write a book aimed at helping agile teams be more successful at delivering business value using tests that the business can understand. We want to help testers and quality assurance (QA) professionals who have worked in more traditional development methodologies make the transition to agile development. Weve figured out how to apply--on a practical, day-to-day level--the fruits of our own experience working with teams of all sizes and a variety of ideas from other agile practitioners. Weve put all this together in this book to help testers, quality assurance managers, developers, development managers, product owners, and anyone else with a stake in effective testing on agile projects to deliver the software their customers need. However, weve focused on the role of the tester, a role that may be adopted by a variety of professionals. Agile testing practices arent limited to members of agile teams. They can be used to improve testing on projects using traditional development methodologies as well. This book is also intended to help testers working on projects using any type of development methodology. Agile development isnt the only way to successfully deliver software. However, all of the successful teams weve been on, agile or waterfall, have had several critical commonalities. The programmers write and automate unit and integration tests that provide good code coverage. They are disciplined in the use of source code control and code integration. Skilled testers are involved from the start of the development cycle and are given time and resources to do an adequate job of all necessary forms of testing. An automated regression suite that covers the system functionality at a higher level is run and checked regularly. The development team understands the customers jobs and their needs, and works closely together with the business experts. People, not methodologies or tools, make projects successful. We enjoy agile development because its values, principles, and core practices enable people to do their best work, and testing and quality are central to agile development. In this book, we explain how to apply agile values and principles to your unique testing situation and enable your teams to succeed. We have more about that in Chapter 1, "What Is Agile Testing, Anyway?" and in Chapter 2, "Ten Principles for Agile Testers." How We Wrote This Book Having experienced the benefits of agile development, we used agile practices to produce this book. As we began work on the book, we talked to agile testers and teams from around the globe to find out what problems they encountered and how they addressed them. We planned how we would cover these areas in the book. We made a release plan based on two-week iterations. Every two weeks, we delivered two rough-draft chapters to our book website. Because we arent co-located, we found tools to use to communicate, provide "source code control" for our chapters, deliver the product to our customers, and get their feedback. We couldnt "pair" much real-time, but we traded chapters back and forth for review and revision, and had informal "stand-ups" daily via instant message. Our "customers" were the generous people in the agile community who volunteered to review draft chapters. They provided feedback by email or (if we were lucky) in person. We used the feedback to guide us as we continued writing and revising. After all the rough drafts were done, we made a new plan to complete the revisions, incorporating all the helpful ideas from our "customers." Our most important tool was mind maps. We started out by creating a mind map of how we envisioned the whole book. We then created mind maps for each section of the book. Before writing each chapter, we brainstormed with a mind map. As we revised, we revisited the mind maps, which helped us think of ideas we may have missed. Because we think the mind maps added so much value, weve included the mind map as part of the opening of each chapter. We hope theyll help you get an overview of all the information included in the chapter, and inspire you to try using mind maps yourself. Our Audience This book will help you if youve ever asked any of the following excellent questions, which weve heard many times: If developers are writing tests, what do the testers do? Im a QA manager, and our company is implementing agile development (Scrum, XP, DSDM, name your flavor). Whats my role now? Ive worked as a tester on a traditional waterfall team, and Im really excited by what Ive read about agile. What do I need to know to work on an agile team? Whats an "agile tester"? Im a developer on an agile team. Were writing code test-first, but our customers still arent happy with what we deliver. What are we missing? Im a developer on an agile team. Were writing our code test-first. We make sure we have tests for all our code. Why do we need testers? I coach an agile development team. Our QA team cant keep up with us, and testing always lags behind. Should we just plan to test an iteration behind development? Im a software development manager. We recently transitioned to agile, but all our testers quit. Why? Im a tester on a team thats going agile. I dont have any programming or automation skills. Is there any place for me on an agile team? How can testing possibly keep up with two-week iterations? What about load testing, performance testing, usability testing, all the other "ilities"? Where do these fit in? We have audit requirements. How does agile development and testing address these? If you have similar questions and youre looking for practical advice about how testers contribute to agile teams and how agile teams can do an effective job of testing, youve picked up the right book. There are many "flavors" of agile development, but they all have much in common. We support the Agile Manifesto, which we explain in Chapter 1, "What Is Agile Testing, Anyway?" Whether youre practicing Scrum, Extreme Programming, Crystal, DSDM, or your own variation of agile development, youll find information here to help with your testing efforts. A User Story for an Agile Testing Book When Robin Dymond, a managing consultant and trainer who has helped many teams adopt lean and agile, heard we were writing this book, he sent us the user story hed like to have fulfilled. It encapsulates many of the requirements we planned to deliver. Book Story 1 As a QA professional, I can understand the main difference between traditional QA professionals and agile team members with a QA background, so that I can begin internalizing my new responsibilites and deliver value to the customer sooner and with less difficulty Acceptance conditions: My concerns and fears about losing control of testing are addressed. My concerns and fears about having to write code (never done it) are addressed. As a tester I understand my new value to the team. As a tester new to Agile, I can easily read about things that are most important to my new role. As a tester new to Agile, I can easily ignore things that are less important to my new role. As a tester new to Agile, I can easily get further detail about agile testing that is important to MY context. Were I to suggest a solution to this problem, I think of Scrum versus XP. With Scrum you get a simple view that enables people to quickly adopt Agile. Ho Details ISBN0321534468 Author Janet Gregory Short Title AGILE TESTING Language English ISBN-10 0321534468 ISBN-13 9780321534460 Media Book Format Paperback Illustrations Yes Year 2009 Imprint Addison-Wesley Educational Publishers Inc Subtitle A Practical Guide for Testers and Agile Teams Place of Publication New Jersey Country of Publication United States Edition 1st Edited by Santiago Martinez-Jimenez Birth 1964 Death 1817 Affiliation Assistant Professor of Clinical Radiology, Thoracic Radiology Section, University of Missouri-Kansas City, St. Lukes Hospital Position Assistant Professor of Clinical Radiology, Thoracic Radiology Section Qualifications MD AU Release Date 2009-01-15 NZ Release Date 2009-01-15 US Release Date 2009-01-15 UK Release Date 2009-01-15 Pages 576 Publisher Pearson Education (US) Series Addison-Wesley Signature Series (Cohn) Publication Date 2009-01-15 DEWEY 005.14 Audience Professional & Vocational We've got this At The Nile, if you're looking for it, we've got it. With fast shipping, low prices, friendly service and well over a million items - you're bound to find what you want, at a price you'll love! TheNile_Item_ID:127506265;

Price: 50.4 AUD

Location: Melbourne

End Time: 2024-11-16T02:07:25.000Z

Shipping Cost: 16.47 AUD