" If I asked one of my Chrome testers any question..."Does this mean that EVERY Chrome tester should be able to answer EVERY question, or that there should exist A Chrome tester for EVERY question?
I suppose the key idea is that WIDELY is more critical than DEEPLY to a tester. For example, a Chrome tester should know every question (or most questions) about how to use Chrome from the view of end users.
I agree with your post. However, this implies that the same person may not be able to play both roles. This is against much of the current thinking in agile - where team members are supposed to be able to contribute based on the need - developers doing testing and testers doing development.
Jac, I think every Chrome tester should be a slam dunk product expert. Everyone will have features they understand better than others, but I want them all to be expert on the entire breadth of functionality the product offers.
The ideal situation would be that if any of my testers moves to another team, we wouldn't miss them (at least professionally).
Hi James, its an amazing post. I learned to believe that a tester is more like a generalist. Tester should be aware of all the aspects of the application under test and should be ready to talk about it even at 4:00 AM in the morning.Thanks for sharing the ingredient 1 i.e. Product expertise
"Chrome tester should be a slam dunk product expert" - I agree.How about chrome testing manager's level of product expertise ? Should I have to expect the same level of expertise from him ??
Hi James Thanks for the post. As you said a testers should be product experts who should be good in technology and business but the challenge is how will you develop these Test product experts? There is huge crowd of so called Testers who doesnt even know a single programming langauge. Even If you find one they dont want to be in testing and always want to be a programmer as Testing is not considered part of software development(hope not in Google atleast :) ) and its a thankless job.
"The ideal situation would be that if any of my testers moves to another team, we wouldn't miss them (at least professionally)."That puts on the table how Google testers share they knowledge? Do you encourage them to talk about product also during their pool games, ps3 sessions, do they have to take lunch or coffee (smoke) break together?How do testers share knowledge except the written stuff (product wikkies and other forms of written data)?
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.