Test Peer Review

Today I have been thinking about peer review of testing work. How as testers we need to ensure that our work gets reviewed by others to make our work even better. I added some thoughts to a Google Jam board and have transferred these brief notes to sections in this blog post. My context of this is an agile delivery team.

Why would you want to get a review?

• To ensure you have the same shared understanding of the product.
• To improve how you test.
• To find gaps in your test coverage.
• Enhanced collaboration in your own team and across teams.
• A sense of belonging in the team.
• Increased learning.

Things you may want to get reviewed

• Test Strategies / Plans
• Your understanding of the product.
• Exploratory testing session.
• Regression Pack.
• What you automate / not automate

Who can be involved in the review?

• Test engineer in your own team
• Developers
• Product Owner
• UX / Tech authors
• Test engineer in a different team