Challenging Your Project’s Testing Mindsets - Joe DeMeyer
Participating on a project as a Tester has some interesting contrasts and some unexpected experiences when compared to participating as a Developer. Having experienced both, I was most surprised with skepticism, concern, general invisibility, and subtle questions about my qualifications as a Tester. It seemed because I was a Tester, I had no credibility.The start of the project is the best time to make an impression, establish your identity, and build credibility. Every Tester knows this but many times other priorities interfere with establishing a foundation for working with other team members and providing value to the project as a Tester. In this session, I present an approach to challenging mindsets and establishing credibility: be available, visible, and vocal. Be available to meet team members, be visible at introductory meetings, be vocal about the role of testing in your project. Building upon these lays the foundation for participation in key meetings, improving testability, getting bugs fixed, and engaging team members in testing. The session includes tips for participating in requirements, design, and code reviews. It concludes with methods of building credibility with your testing team, using delegation to build new test leaders, and advocating for testability in project products.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (15)
Similar to Challenging Your Project’s Testing Mindsets - Joe DeMeyer
Similar to Challenging Your Project’s Testing Mindsets - Joe DeMeyer (20)
More from QA or the Highway
More from QA or the Highway (20)
Recently uploaded
Recently uploaded (20)
Challenging Your Project’s Testing Mindsets - Joe DeMeyer
- 3. About Me • Lift Trucks and Electrometers • Insurance 3/14
- 4. Mindsets • Beliefs Based on Experience • Project Mindsets • Challenging A Mindset – Available – Visible – Vocal Unit Testing Tester Qualifications Test Coverage Joining a Project Meeting Attendance Product Testability Test Reporting Project Work 4/14
- 5. Be Available • Be Actively Available – The Available Mindset – Meet Everyone – Seek Invitations • Meeting Purpose – Domain Education – Project Changes – Test Ideas – Testability 5/14
- 6. Be Available • Trade Off – Multiple meetings at different times – Move forward with less, spend time later – Less impactful, probing tests – Invalid defects – Have developers attend fewer meetings? • Pilot • When Do You Want to Learn About Your Project and its Products? 6/14
- 7. Session Tangent • Which one did the Tester color? 7/14
- 8. Be Visible • Visible Mindset • Shine the Light – You – Project Participation – Project Products • Continuous Profiling 8/14 1 2 3 4 5
- 9. Be Visible • Requests for Information • Seek Scenarios and Demonstrate Them • Demonstrate Knowledge of System Behavior 9/14
- 10. Be Vocal • Vocal Mindset • Product or Schedule Opportunities • Project Impacts 10/14 1 2 3 4 5
- 11. Be Vocal • Meet with Your Team – Testing Challenges – Project/Product Changes – Project Team Members • Provide Feedback • Lead Opportunities 11/14
- 12. Challenging Mindsets • Consistent and Patient • Consider How to Convey Your Ideas and Suggestions • Be Available, Visible, and Vocal – Challenge Project Mindsets – Challenge Enterprise Mindsets • Create Your Tester Identity 12/14
- 13. Thanks for attending this session! Please fill out an evaluation form. 13/14
- 14. Questions 14/14
Editor's Notes
- Twitter: @DevToTest Blog: opentoscrutiny.wordpress.com
- Testers don’t have boundaries, can’t cover everything, and they cover what is important. Testing may not be pretty but it is valuable. Image Source: http://www.teddybears.org/coloringPages.htm Coloring: Joe DeMeyer