Mobil Weekend - Evolution of the Test Team
1 like313 views
The document outlines the author's journey in building and evolving a mobile test team, detailing the challenges faced, processes introduced, and lessons learned. It emphasizes the importance of collaboration between developers and testers, the need for automation, and iterative improvement in testing practices. Key takeaways include scaling testing efforts accordingly, embracing CI/CD practices, and the integration of testing into development processes.
More Related Content
Similar to Mobil Weekend - Evolution of the Test Team (20)
Mobil Weekend - Evolution of the Test Team
- 1. HOW DID I BUILD UP A MOBILETESTTEAM,THEN BREAK IT DOWN? OR THE EVOLUTION OF THE TEST TEAM Csaba Szabó Senior Test Engineer
- 2. WHERE AREYOU? WHAT’STHIS? • Story, learnings, retrospective • How (not) to test mobile apps • Who is it for? • What won’t be? 2
- 3. WHY ME? • BME - LogMeIn - Distinction - Skyscanner • I wanted to be a mobile app developer • From zero, with lots of failures • Team leader: 1 → 6 → 3 → ? 3
- 4. THE BEGINNING • My first task - manual testing • Little projet - unit test? • I had to introduce processes • You can be the bad guy (if you do it badly) “Developers and testers should be friends.” 4
- 5. WHAT DID I INTRODUCE? • JIRA: bug, workflow • Test documentation (NO) • Continues builds and version numbering • Fiddler, the Swiss-Knife (Dixie) 5
- 6. WHAT’S NEXT? • Innovation! • “Ask, don’t predict” “One sentence” • What not? UI testing, unit test writing, static code analysis • Then what? 6
- 7. • CI/CD - what’s the goal? • Gitflow, pull request, build script • Jenkins vs ? • Show, ask, iterate • Test → DevOps 7
- 8. UITESTING • (!) you can lose months We had > 500 UI tests • Process, maintenance, close to the code • Side effect: screenshot 8
- 9. THE CODE ANDTHETESTER • “I'm an engineer” • Catch the bug at the end (app) Catch the bug at the beginning (code) • Change the roles • Test → Dev 9
- 10. WHERE WE DID MISTAKES • Too much manual testing • Scaling problems • “Automation will solve it” 10
- 11. HOW WE FIXED IT • Test + Dev = Engineer • Focus on Pull requests • Bigger developer responsibility • Crowdsource and beta testing 11
- 12. HOW BIGS ARE DOING IT? • Scaling - they have different problems and solutions • Google: SE > SET >TE • Facebook: dogfood and internal crowdsource • Spotify: model-based testing (funfact: iOS-Test-Generator) 12
- 13. IF I WOULD HAVE MORETIME • Scale the testing for your project • More CI / CD • RCA • More UI testing • Release management and monitoring 13
- 14. SUMMARISING • Manual testing is important, but can be too much Scale it to your project • Testing is complex and far-reaching • Good developer tests • Introduce automation iteratively 14
- 15. THANKYOU • Questions? Csaba Szabó - Skyscanner [email protected] http://www.skyscanner.net/jobs/ Our new office: https://www.fb.com/hashtag/skyscannerbp 15