Try Blinkist to get the key ideas from 7,500+ bestselling nonfiction titles and podcasts. Listen or read in just 15 minutes.
Start your free trialBlink 3 of 8 - The 5 AM Club
by Robin Sharma
Agile Testing by Janet Gregory and Lisa Crispin offers practical guidance on how to adapt testing practices for agile projects. It covers techniques for effective testing in an iterative and collaborative environment.
In Agile Testing by Janet Gregory and Lisa Crispin, we are introduced to the concept of agile testing, a methodology that emphasizes the importance of testing throughout the software development lifecycle. The authors argue that traditional testing methods, which are often performed at the end of the development cycle, are not suitable for agile environments. Instead, they advocate for a shift-left approach, where testing is integrated into every stage of the development process.
The book begins by outlining the core principles of agile testing, such as the importance of collaboration, continuous feedback, and the ability to respond to change. The authors emphasize the need for testers to work closely with developers, business analysts, and other stakeholders to ensure that the software meets the desired quality standards.
Gregory and Crispin introduce the concept of the Agile Testing Quadrants, a model that categorizes different types of tests based on their purpose and the target audience. The authors explain that Quadrant 1 tests, which include unit tests and component tests, are developer-facing and focus on ensuring the code functions as intended. Quadrant 2 tests, such as exploratory testing and usability testing, are user-facing and aim to validate the product's functionality and user experience.
Quadrant 3 tests, which include performance testing and security testing, are technology-facing and focus on non-functional aspects of the software. Quadrant 4 tests, such as regulatory compliance testing and release-readiness testing, are business-facing and ensure that the software meets the necessary business requirements. By understanding these quadrants, agile teams can better plan and execute their testing efforts.
As the book progresses, Gregory and Crispin delve into the challenges that testers may face in an agile environment. They discuss issues such as the lack of documentation, tight release schedules, and the need for continuous testing. However, the authors also provide practical solutions to these challenges, such as using automation to speed up testing, adopting exploratory testing techniques, and leveraging the power of cross-functional teams.
Furthermore, the authors emphasize the importance of metrics in agile testing. They caution against using traditional metrics, such as the number of test cases executed, and instead advocate for metrics that focus on the value delivered, such as defect detection rate and customer satisfaction. By using the right metrics, agile teams can better assess the effectiveness of their testing efforts.
In the final sections of Agile Testing, Gregory and Crispin stress the importance of continuous improvement in agile testing. They encourage testers to embrace a mindset of learning and adaptation, to regularly reflect on their processes, and to seek feedback from their team members and stakeholders. The authors also highlight the role of the agile testing coach, who can help teams navigate the challenges of agile testing and continuously improve their practices.
In conclusion, Agile Testing by Janet Gregory and Lisa Crispin provides a comprehensive guide to implementing effective testing practices in an agile environment. By emphasizing collaboration, flexibility, and continuous improvement, the book equips testers and agile teams with the tools they need to deliver high-quality software in a fast-paced, ever-changing world.
Agile Testing by Janet Gregory and Lisa Crispin is a comprehensive guide that explores the principles and practices of testing in an agile environment. It offers practical advice and real-world examples to help testers and teams adapt to the fast-paced and collaborative nature of agile development. Whether you're new to agile or looking to improve your testing processes, this book provides valuable insights to ensure high-quality software delivery.
Agile Testing (2008) is a comprehensive guide for anyone involved in software testing within an agile team. Here's why this book is worth reading:
It's highly addictive to get core insights on personally relevant topics without repetition or triviality. Added to that the apps ability to suggest kindred interests opens up a foundation of knowledge.
Great app. Good selection of book summaries you can read or listen to while commuting. Instead of scrolling through your social media news feed, this is a much better way to spend your spare time in my opinion.
Life changing. The concept of being able to grasp a book's main point in such a short time truly opens multiple opportunities to grow every area of your life at a faster rate.
Great app. Addicting. Perfect for wait times, morning coffee, evening before bed. Extremely well written, thorough, easy to use.
Try Blinkist to get the key ideas from 7,500+ bestselling nonfiction titles and podcasts. Listen or read in just 15 minutes.
Start your free trialBlink 3 of 8 - The 5 AM Club
by Robin Sharma
What is the main message of Agile Testing?
The main message of Agile Testing is that software testing should be an integral part of the agile development process.
How long does it take to read Agile Testing?
The reading time for Agile Testing varies depending on the reader's speed. The Blinkist summary can be read in just 15 minutes.
Is Agile Testing a good book? Is it worth reading?
Agile Testing is worth reading for software professionals interested in improving their agile testing practices.
Who is the author of Agile Testing?
The authors of Agile Testing are Janet Gregory and Lisa Crispin.