Coaching Teams to Modern Test Management

One year of building a product, from quarterly to monthly releases. From 27 days to 19 minutes release lead time. 13 reusable test charters, 1851 programmatic tests executed in pipelines frequent enough to produce 50 000 test results a day. No bug reports written and zero bugs policy for releasing. This describes my current team in a nutshell.

Modern test management relies on frequent, moving up to continuous releases. Working from a known good baseline taking small steps following the change allows for a new way of managing testing. And while numbers of programmatic tests are impressive, the bugs they miss that exploratory testing - also using automation - finds are more impressive. We say that the large numbers of programmatic tests do 10% of the testing the team does. 90% of the work is keeping test systems up to par with the latest scope of system we deliver and attending to results gap programmatic tests inherently include.

In this talk, we learn to manage testing maintaining agency - the capacity of individuals to act independently and make their own free choices. This is not a story about managing testing based on sessions. This is a story of working with product owners to identify gaps and assign responsibilities, working with teams to make the right skills available for different kinds of testing tasks across roles, identifying testing roadblocks with data deep dives and creating space where test design and test execution always come together while navigating corporate documentation requirements. Practices to this are frequent deliveries, following change, whole-team test automation, bug reports as conversations, pair and ensemble testing, and feature checklists. We need to ensure we pay attention to both testing of today and testing of the future.

Transcript

1. @maaretp @maaretp@mas.to by Maaret Pyhäjärvi Coaching Teams to Modern Test Management
2. @maaretp @maaretp@mas.to A Tale of a Team (and its neighbor) 27 days to 19 minutes release lead time 13 reusable test charters 1851 programmatic tests with 50 000 results a day no written bug reports zero bugs policy – fix (test) and forget 10% of testing is automated Contemporary ExploratoryTesting Testing is too important to be left just for testers. And too important to be left without testers. Developers CAN test and want to test.
3. @maaretp @maaretp@mas.to The Better Teams SPEC FEEDBACK REGRESSION GRANULARITY GUIDANCE UNDERSTANDING MODELS SERENDIPITY Testing as artifact creation EXAMPLES EXPERIMENTS Testing as performance
4. @maaretp @maaretp@mas.to The Better Teams Unit Tests Service Tests UI Tests
5. @maaretp @maaretp@mas.to The Better Teams Unit Tests Service Tests UI Tests Mocks, Stubs, Spys and Fakes Real Integrations
6. @maaretp @maaretp@mas.to The Better Teams Unit Tests Service Tests UI Tests Mocks, Stubs, Spys and Fakes Real Integrations Perfor- mance Usability Functio- nality Security
7. @maaretp @maaretp@mas.to The Better Teams Unit Tests Service Tests UI Tests Mocks, Stubs, Spys and Fakes SPEC FEEDBACK REGRESSION GRANULARITY GUIDANCE UNDERSTANDING MODELS SERENDIPITY Real Integrations Perfor- mance Usability Functio- nality Security Testing as artifact creation EXAMPLES EXPERIMENTS Testing as performance impact intent
8. @maaretp @maaretp@mas.to Modern Test Management relies on Frequent to Continuous Releases Known Good Baseline
9. @maaretp @maaretp@mas.to 10 % - Keep Programmatic Tests Green 90 % - Explore for results (information / bugs) and learning (new programmatic tests) Failing test is an invitation to explore!
10. @maaretp @maaretp@mas.to Agency the capacity of individuals to act independently and make their own free choices
11. @maaretp @maaretp@mas.to Pro Product Owners are the new test managers!
12. @maaretp @maaretp@mas.to working with product owners to identify gaps and assign responsibilities working with teams to make the right skills available for different kinds of testing tasks across roles identifying testing roadblocks with data deep dives creating space where test design and test execution always come together …while navigating corporate documentation requirements Coaching?
13. @maaretp @maaretp@mas.to Practices Frequent deliveries Following change Whole-team test automation Bug reports as conversations Pair and ensemble testing (and programming) Feature checklists
14. @maaretp @maaretp@mas.to Short-term Long-term AVAILABILITY TIMELINE Productive Generative RESULTS Break illusions in a timely fashion Capture notes in test automation Test automation people can use when we’re gone Improve skills of everyone Improve your skills Learn to pair & ensemble
15. @maaretp @maaretp@mas.to 2020 2016 MIATPP Most Influential Agile Testing Professional Person #PayToSpeak #TechVoices #EnsembleTesting #EnsembleProgramming #StrongStylePairing #ExploratoryTesting #TestAutomation #ModernAgile #AwesomeTesters Maaret Pyhäjärvi (from Finland) Email: maaret@iki.fi Twitter: @maaretp Web: maaretp.com Blog: visible-quality.blogspot.fi (please connect with me through Twitter or LinkedIn) 2019 - 2022 https://exploratorytestingacademy.com Ohjelmistotestaus ry https://techvoices.org