Talk at Rio de Janeiro Ministry of Testing Meetup: Testing as Part of the Team Culture
•
0 likes•222 views
Ministry of Testing Meetup | Rio de Janeiro , Brazil | 18th September 2018 This presentation is about different changes that were implemented when an interdisciplinary team developing a product started adopting testing as part of their team culture. During the presentation, Claudia will share what they have learned from a testing perspective and also what other lessons were learned beyond testing that helped them build a team culture. This story is set during the process of building a multi-platform UI prototyping tool (mainly) for interaction designers. It covers a six-year period during which there have been eleven major releases and several intermediate releases. The team, fully dedicated to building the product, consists of highly qualified and experienced professionals: developers (5), interaction designers (1), visual designers (1), technical writers (1), and testers (1).
Recommended
More Related Content
Similar to Talk at Rio de Janeiro Ministry of Testing Meetup: Testing as Part of the Team Culture
Similar to Talk at Rio de Janeiro Ministry of Testing Meetup: Testing as Part of the Team Culture (20)
More from Claudia Badell
More from Claudia Badell (20)
Recently uploaded
Recently uploaded (20)
Talk at Rio de Janeiro Ministry of Testing Meetup: Testing as Part of the Team Culture
- 1. @claubs_uy TESTING AS PART OF THE TEAM CULTURE Eng. Claudia Badell claudia@claudia-badell.com @claubs_uy September 18, 2018｜Rio de Janeiro
- 2. @claubs_uy Speaker • Agile Testing Days (Germany & USA) • ExpoQA (Spain) • Meetups (Uruguay) • Next Generation Testing Conference (England) • TestingUy (Uruguay) • VLCTesting (Spain) • WCSQ (Perú) Co-organizer testinguy.org • +12 years of experience in testing • Senior Quality Engineer • Test Manager • Tester • Business Analyst • Teacher at School of Engineering, UdelaR • Certified Scrum Master • Agile Testing 101 tutorial with Janet Gregory & Lisa Crispin • Rapid Software Testing course with Michael Bolton • Association for Software Testing courses (Foundations & Bug Advocacy) • ISTQB Foundation Computer Engineer Quality time with my family & friends, walk, craft beer Travel freak valijasready.com
- 3. @claubs_uy AGENDA 1 CONTEXT 4 LESSON 3 Take ownership of your process 2 5 LESSON 1 Build a common understanding about testing LESSON 4 Testing is a team responsibility 3 6 LESSON 2 Adapt your testing strategies as a team approach LESSON 5 Nourish your team culture
- 4. @claubs_uy AGENDA 1 CONTEXT 4 LESSON 3 Take ownership of your process 2 5 LESSON 1 Build a common understanding about testing LESSON 4 Testing is a team responsibility 3 6 LESSON 2 Adapt your testing strategies as a team approach LESSON 5 Nourish your team culture
- 5. @claubs_uy • Developers (5) • Visual designers (1) • Interaction designers (1) • Technical writers (1) • Testers (1) THE TEAM Testing is performed by most of us
- 6. @claubs_uy THE PRODUCT UNDER TEST • In the market since 2012 • 11 major releases, several intermediate updates and silent updates
- 8. @claubs_uy I’m great at this one thing and familiar with all this other stuff.
- 9. @claubs_uy AGENDA 1 CONTEXT 4 LESSON 3 Take ownership of your process 2 5 LESSON 1 Build a common understanding about testing LESSON 4 Testing is a team responsibility 3 6 LESSON 2 Adapt your testing strategies as a team approach LESSON 5 Nourish your team culture
- 10. @claubs_uy Build a common understanding about testing #1
- 11. @claubs_uy • Internal trainings • Kick-off testing meetings • Follow-up testing meetings • Early Testing Build a common understanding about testing
- 12. @claubs_uy Adapt your testing strategies as a team approach #2
- 13. @claubs_uy Adapt your testing strategies as a team approach Checklists to support exploratory testing
- 14. @claubs_uy CHECKLISTS • Used as input to test when doing exploratory testing • One per each feature or module being tested • Elaborated between the tester and the developer(s) involved in the feature • Included test ideas and variables to cover, kinds of errors we were looking for and solutions risks
- 15. @claubs_uy • Writing checklists with the feature developers helped identify testing variables from inside the code • The testing variables and ideas to cover were explicitly shared within the team • It was difficult to represent dependent test variables • We reused feature-checklists to avoid re-thinking test ideas, conditions and variables from scratch CHECKLISTS
- 16. @claubs_uy Adapt your testing strategies as a team approach Mind maps to support exploratory testing
- 17. @claubs_uy A mind map to describe a mind map
- 18. @claubs_uy • Organize and visualize ideas • Identify dependencies • Discuss ideas • Enhance creativity • Share knowledge MIND MAPS HELP US
- 19. @claubs_uy We build a mind map for each feature
- 20. @claubs_uy A mind map includes test conditions, ideas and variables to cover a feature
- 21. @claubs_uy
- 22. @claubs_uy We don’t track sessions
- 23. @claubs_uy We use mind maps as reference for exploratory testing sessions
- 24. @claubs_uy We reuse mind maps to avoid re-thinking test ideas, conditions and variables from scratch
- 25. @claubs_uy Mind maps are extended or updated according to changes in the product
- 26. @claubs_uy • Repository • File naming conventions STORING OUR MIND MAPS
- 27. @claubs_uy Adapt your testing strategies as a team approach • A proactive attitude to update and extend the testing artifacts according to features’ changes • A repository with a defined folder hierarchy and file naming conventions • Guidelines and nomenclature conventions • A guardian of the strategy In all strategies we have
- 28. @claubs_uy Adapt your testing strategies as a team approach • our bug tracker workflow • our knowledge of the product beyond our specific activities • the testing effort required for a release • the impact that a fix has from the testing effort perspective As a team, we gained a deeper understanding of We improved
- 29. @claubs_uy Take ownership of your process #3
- 30. @claubs_uy Take ownership of your process • Weekly meetings, instead of daily stand-up meetings • Design meetings
- 31. @claubs_uy Testing is a team responsibility #4
- 32. @claubs_uy Be open minded to adapt your role Testing is a team responsibility
- 33. @claubs_uy Testing is a team responsibility The tester in the team as a facilitator and evangelist
- 34. @claubs_uy Testing is a team responsibility Be flexible enough to adapt and wear other hats depending on the needs of the product and the team
- 36. @claubs_uy Nourish your team culture Communication Transparency Collaboration Being eager to Learn Reflection Team building activities Constructive feedback Motivation Learning from mistakes Flexibility Involving the affected Respect
- 37. @claubs_uy Nourish your team culture Promote activities to share knowledge across disciplines
- 38. @claubs_uy KEEP CALM AND ENHANCE YOUR TEAM TESTING CULTURE
- 39. @claubs_uy THANKS! Questions? CONTACT: Claudia Badell claudia@claudia-badell.com @claubs_uy September 18, 2018｜Rio de Janeiro