When I try to get developers to do testing, they say it's not their job. What can I do about that?
What is the number one activity testers can do to create a culture of shared responsibility for testing within the team?
Every team is unique but are there blank canvas go to strategies / heuristics which can be used to grow a quality focus?
How can product management support whole team testing with their efforts?
What techniques and tools can help get the whole team involved in testing?
If the whole team tests, what's the future for testers?
Any advice for new testers who are still learning how to test as part of a team and do not feel experienced in the role?
What is the challenge with getting non testers to understand that testing is more than automation?
What would you say are the success criteria for a team that is doing whole team testing?
What are the initial tasks or activities to evaluate if a team/company is ready for whole team testing?
Do you have any tips on how I can introduce cross-company testing sessions to teams who don't interact with the platform much in a fun and engaging way?
Where does automation belong in a sprint?
How have teams incorporated performance testing in whole team testing?
Chapter How can I get developers to make the code more testable?Title
Description
One of the cornerstones of agile development is the whole-team focus on building quality into the software. On high-performing teams, everyone takes responsibility for testing, regardless of their official role or self-identified specialities. The DevOps movement has built on this, putting even more focus on delivery teams collaborating with Operations and other teams to build testable infrastructure and enabling continuous delivery.Â
In this AMA, Lisa answered questions about how whole-team testing works in practice. If you’re wondering how in the world you get non-testers interested in doing work that they’ve purposely avoided in the past, or interested in newer practices that involve more of the delivery team, such as pair and mob testing.Â
mabl are sponsored this AMA.
mabl is the most reliable codeless UI testing service available, enabling continuous testing with an auto-healing automation framework and maintenance-free test infrastructure. Using proprietary machine learning models to automatically identify application issues, including javascript errors, visual regressions, broken links, increased latency, and more,
mabl brings traditional UI testing to the modern age.Find out more about
 mabl.
Lisa Crispin
Quality consultant
Lisa Crispin is the co-author, with Janet Gregory, of More Agile Testing: Learning Journeys for the Whole Team (2014), Agile Testing: A Practical Guide for Testers and
Agile Teams (2009), the LiveLessons Agile Testing Essentials video course, and “The Whole Team Approach to Agile Testing” 3-day training course. She co-authored Extreme Testing (2002) with Tip House. She is a contributor to Experiences of Test Automation by Dorothy Graham and Mark Fewster (Addison-Wesley, 2011), Beautiful Testing (O’Reilly, 2009) and other books. Lisa was voted by her peers as the Most Influential Agile Testing Professional Person at Agile Testing Days in 2012. She enjoys helping people find ways to build more quality into their software products, as well as hands-on testing. Please visit www.lisacrispin.com and www.agiletester.ca for more.
