Download to read offline
Uploaded byMaaret Pyhäjärvi
Selenium Conf: Patterns to Whole Team Test Automation Transformation
The document discusses test automation transformation and lessons learned from a team's experience improving their test automation process. Some key points: - The team was able to improve test automation maturity and increase speed of releases, decrease time to release, and improve productivity, despite not having an explicit test automation strategy or careful tool selection. - Perceived success factors included whole team effort, expert team members, self-motivated team members, allowing time for learning, and choosing the right test tools and infrastructure. - An incremental approach, observing and optimizing processes, and an internal open-source community mindset also contributed to the team's success in improving their test automation capabilities.
Selenium Conf: Patterns to Whole Team Test Automation Transformation
- 1. @maaretp Patterns to WholeTeam Test Automation Transformation by Maaret Pyhäjärvi
- 2. @maaretp ‘plexus’ particularly python libraryto drive hardware interfaces in embedded systems js/ts
- 3. @maaretp A published storyfrom… 2019 https://www.academia.edu/49495368/Test_Automation_Process_Improvement_in_a_DevOps_Team_Experience_Report
- 4.
- 5. @maaretp We did particularly wellwith our Test Automation (TA) WHY?
- 6.
- 7.
- 8.
- 9. @maaretp Conflict with previousresearch! • No explicit test automation strategy • No careful tool selection • No measuring quality and performance of TA • No explicit guidelines “…relaxed, verbally communicated strategy without strict rules and processes relying on developers’ voluntary participation.We consider this an unusual success with TAPI …
- 10. @maaretp High satisfaction andmaturity (self-reported 2019) (2021) - Increasing speed to release (from 2-4 releases to 9 releases) (from 1 release to 9 releases) - Decreasing time to making release (from 5 days to 4 hours) (from 34 days to 2 days) - Improving team productivity (11 team members, 2917 code changes out of 6583 for 3 teams) (significant investment) - Shared platform work efficiency - Sustainable test automation maintenance effort - Finding relevant issues (new product in days, MANY timing issues and regressions) (new product in days, MANY new issues) - High satisfaction of customers (167 support issues, 1 escalation for millions of customers) (new product, few customers) - High test efficiency (213 708 tests in single working day) (~100 tests each night, green within day) - Reasonable investment in test automation process improvement (ehh, none) (significant)
- 11.
- 12. @maaretp Perceived Success Factors DimensionFactor Human Whole team effort Expert team members Self-motivated team members Organizing Allow time for learning curve Internal open-source community mindset Technical Test tool choice and architecture Testlab infrastructure Product testability Telemetry Process Incremental approach Process observation and optimization
- 13. @maaretp Moving from specialist languageto generalist language
- 14.
- 15. @maaretp Showcase progress made ofcontinuous flow of small changes
- 16. @maaretp Choose to releasebased on automation no matter how little test automation there is * Explore by following change
- 17. @maaretp Growing individual competencies bysharing YOUR screen when working together
- 18.
- 19. @maaretp Semantic selectors over position-based,but I just wanted to try them out The vscode coloring bug bothers me but not enough
- 20. @maaretp Contemporary Exploratory Testing Improved Understanding ofSuccess No manual and automated testing
- 21. @maaretp 2020 2016 MIATPP Most InfluentialAgile 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, 2020, 2021 https://exploratorytestingacademy.com Ohjelmistotestaus ry https://techvoices.org