Download as PDF, PPTX
Uploaded byTEST Huddle
Growing a Company Test Community: Roles and Paths for Testers
The document outlines the approach taken by Alex Schladebeck at Bredex GmbH regarding the roles and development of testers within a software company. It covers aspects of defining and hiring tester roles, training methodologies, and creating a vibrant test community. Key takeaways emphasize the importance of communication, continuous investment in skills, and fostering a supportive environment for professional growth.
More Related Content
Similar to Growing a Company Test Community: Roles and Paths for Testers
![[Paul Holland] Trends in Software Testing](https://cdn.slidesharecdn.com/ss_thumbnails/paulhollandtrendsinswtesting-140717230533-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Growing a Company Test Community: Roles and Paths for Testers
- 1.
- 2. Introductions • I am … – A tester, Head ofTest Consulting, Product Owner • Bredex is – A German software developmentcompany – With a strong focus on quality Training Development Testing
- 3.
- 4.
- 5.
- 6.
- 7. Agenda – how we deal with my problems • Defining roles for testers •Hiring testers • Training testers • Creating and fostering a test community
- 8. What flavours of tester are there? Functional Test Consultant -Closer work with RE/PO - User perspective in testing - Trained in ET and SBTM - Top-Down for automation - Mentoring and Reviews Technical Test Consultant - Closer work with developers - Technical aspects of testing - Trained in ET and SBTM - Bottom-Up for automation - Mentoring and Reviews
- 9.
- 10.
- 11.
- 12.
- 13. The interview process Aim: to find out whether theapplicant has the potential to be trained as a test consultant
- 14. Tools for the interview Exercise on exploratory testing(20m) Exercise on technical reading and resumé (20m) Conversation and discussion (60m)
- 15. Exploratory testing • What doesthe application do? • Who could use it? • What would be important to test in it? • How could priorities be determined? • Did you find any problems? • How do you rate the usability?
- 16.
- 17. Read and summarize an article • German language • Abouttest automation • Includes info on test design, agile processes, component recognition, ...
- 18. Conversation and discussion Own ideas and infoon testing Discussion of exercises Company, Person, CV
- 19.
- 20. Tabula Rasa Tester Theory ISTQB book ISTQB cert Jubula Java for testers Exploratory testing Workshops about testautomation patterns (CI) Four hour tester Code combat
- 21. Tabula Rasa Tester Theory ISTQB book ISTQB cert Jubula Java for testers Exploratory testing Workshops about testautomation patterns (CI) Four hour tester Code combat
- 22.
- 23. Tabula Rasa Tester Theory ISTQB book ISTQB cert Jubula Java for testers Exploratory testing Workshops about testautomation patterns (CI) Four hour tester Practice In project team With mentor Test specification Test automation Exploratory testing Reviews Development processes Social
- 24.
- 25.
- 26.
- 27.
- 28. Keeping the herd together – test team meetup • Empowerlearning and sharing – New topics e.g. books, design patterns, tools – Project and conference reports, discussions – Autonomousworking and variety • Transfer knowledge and who knows what – Multiple contact people • Create co-responsibility, practice coaching, remove fear – Peer reviews – Pairing on activities
- 29. Keeping the herd together – personal contact Index check: one on one conversation - Every two weeks / once a month -What is your happiness index? - What is your “challenge” index? - Autonomy, Mastery, Purpose (Daniel Pink, Drive)
- 30.
- 31. Results à Requirements engineer à Project lead àExternal consulting à Conference talks à Selenium expertise Common understanding Discussion encouraged Self-organised and empowered
- 32. Takeaways • Think about what skills you need and which you need to train • Be prepared to invest continuously •Never underestimate the power of communication and community – foster a good environment @alex_schl alexandra.schladebeck@bredex.de