| OverviewThis is the Safari online edition of the printed book.
"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
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.
Editorial ReviewsProduct Description“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 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. |
Other Readers Also Read | Top Sellers in This Category | Browse Similar Topics | | | Top Level Categories:Sub-Categories: | | | | |
Reader Reviews From Amazon (Ranked by 'Helpfulness') Average Customer Rating: based on 7 reviews. Very valuable resource for every people involved in software testing, 2009-05-15 Reviewer rating: Some authors are good at presenting theories but unable to connect them to practice. Other are good at telling stories from the trenches, but without being able to produce an analysis of the situation and propose some solutions. On the less examined domain of agile testing, Lisa Crispin and Janet Gregory are, luckily for us, presenting a book that covers both the personal experience of being a tester in agile projects and a conceptual vision of the place of quality assurance in software projects. Thus you will find in this book "stories" that comes from past projects and "mind maps" that helps to have a high-level vision of the material of each chapter.
The book offers resource to organize the quality assurance and testing activities in an agile project. It explains also the relationship between test automation and agility. It provides also a part dedicated to the chronicle of the agile testing activities during project life, showing how every member of the team could contribute to quality.
I think however that the more interesting contribution of the book is Testing Quadrants. This concept classifies testing activities depending on their focus (technology or business) and their intent (supporting the team or validating the product). Adding an agile perspective to the original work of Brian Marick, the authors provide resources and examples for each quadrant to make sure that you will cover all the aspects of testing for your project.
This book is certainly a very valuable resource for every people involved in software testing, even if this is not in an agile project. It will also be valuable for ScrumMasters and project managers that have to think on how to integrate the testing activities in their projects. | Excellent purchase, 2009-05-05 Reviewer rating: Agile Testing book is givining me a better point of view for the newer tendency in testing world.
I have read different books about testing but this has been the first in agile topics.
I'm very satisfied with this book. | The definitive guide and reference for how to test on an agile project, 2009-03-22 Reviewer rating: This is an excellent book that deserves to be read by every tester on an agile project--and since agile projects largely try to do away with specific roles, everyone tests, making this a great book for almost anyone on an agile team. The book starts by laying groundwork by defining what agile testing is and describing ten principles for doing it. Part 2 touches on the organizational changes that will be felt by the testing or QA group as the company transitions to agile.
Part 3 is probably the centerpiece of the book. It is structured around four testing quadrants initially conceived of by Agile Manifesto co-author Brian Marick. These quadrants allow Crispin and Gregory to cover a broad range of topics including exploratory, UI, API, usability, performance, stress, and reliability testing. The book definitely goes beyond the basics and the authors don't shy away from challenging topics.
Part 4 covers automation, a topic that should be on the minds of any agile team. One of my favorite sections in this part is the discussion of barriers to automation. The advice here should help many teams overcome some of the resistance created by these barriers. Part 5 is an interesting section that brings the ideas of the book together by walking chronologically through the typical events of an iteration and focusing on the activities of testers at those times. Part 6 concludes with a short list of critical success factors.
I like that this book is both universal and personal. It is chock-full of universal, practical advice but the author's make liberal use of sidebars in which they tell their own personal stories. This combination of telling us how something should be done and then adding detail in the form of how they did it works very well. By the end of the book you have learned a great deal about testing and these two world-class testers.
Very highly recommended. | Great book, long overdue, 2009-02-23 Reviewer rating: The main theme of this book is fitting testing tasks into agile projects, and as such this book really is long overdue. Most agile books are written by programmers for programmers, leaving testers in particular to fend for themselves. No wonder why so many of them feel lost in this world. This book definitely delivers on the promise to ease the transition for testers and QA engineers who suddenly found themselves on an agile project. It has a testing focus and presents things in a way that testers, coming from more traditional process oriented software projects, should understand. The key pillars of practice on which the content of this book stands are improved communication, the whole team approach, agile testing quadrants and automation, so the book efficiently points traditional testers to new knowledge and ideas that they need to focus on to contribute to an agile project. It also provides a solid framework for executing traditional testing tasks in an agile environment without lagging behind the development and causing the project to fall into the "mini-waterfall" trap.
I would also recommend it to project managers and team leaders as they will be able to see the project from the testers' eyes and complement their knowledge about quality on agile projects. As such, it is especially an important reading for teams that consider JUnit the extent of their "testing" process. The book raises valid concerns about commonly overlooked tasks such as test planning, security, performance and usability testing, documentation testing and provides some very practical advice how to plan and execute exploratory testing efficiently. | Great help for transitioning QA analysts to Agile teams, 2009-02-06 Reviewer rating: I'm a QA Manager in a department of 30 testers, most of whom have spent their entire careers on traditional SDLC "waterfall" projects. One of my, perhaps unenviable, tasks is to help transition these folks onto newly formed Agile teams. While I've had success, I wish I had this book sooner!
Crispin and Gregory have created a practical and very readable reference that shines a light on the roles of testers, and testing management -- areas that are often neglected in most of the work that I've found. Perhaps most importantly, they address the fear and apprehension that testers feel when faced with the prospect of joining an Agile team -- the same emotions I've seen (and felt) time and time again.
There's an appropriate mix of high level concepts and low level specifics. The book starts with discussions of principles and mindsets and moves on, in the later chapters to discuss such things as specific techniques of test automation. All along there are anecdotes from interviews with real agile teams and quoted articles from testing luminaries such as Brian Marick, Michael Bolten, et. al.
I've already begun to incorporate much of the material in these books into my own writings and presentations and it's certainly gratifying to see some of my own ideas mirrored. I now have solid references to back them up! I highly recommend this book for testers and testing managers who are planning to start on Agile projects, or who have years of experience on them. There's surely something in this book that will influence you. |
Some information above was provided using data from Amazon.com. View at Amazon > |
| |
|
|
