I loved this post James and have also forwarded it to my team, you are one of the most outright person. This year I want to learn more and more, its always like that but this time I will follow a more structured regime. Majority of the times I do follow the 1 and 2 resolutions as mentioned by you but now I want to focus more on the 3 pointer. Please share your methods and approaches as well that you will be taking for minimizing the repetitive and wasteful testing being performed.
I think Google do a better job than most large technology firms when it comes to publicising known issues, although I guess there's always room for improvement.
I've not looked at ChromeOS but I've delved a little into the Chrome browser bugs and appreciated the input from the Chrome dev team.
Nice to see your user-focussed approach. I've always considered myself to be a user-centric tester (been doing mostly UAT-related testing throughout the last ten years). User experience can easily get pushed down the priority list when it should be right at the forefront
I am really looking forward to read more about your testing practices this year. Great resolution!
Although you sound a bit like you want to emphasize some sort of disconnect between testers and developers. I am convinced that in healthy teams both roles are equally responsible to deliver quality. So, they want to work closely together, listen to each other, and have a sense for the problems the other role deals with. I don't want to sound all touchy feely, my experience is just that some us vs. them does not help the user at all.
And yes, drive testing from the user's perspective! I could not agree stronger!
I am always wondering why companies like Google, Microsoft try to create the hybrid between tester and dev (SDET). Why not a splitting the positions, at least in 3: dev that helps only testers, SDET and testers. Of course everyone should have the same skill but in different percentage. I am a tester that focus on ET a lot so I don't know the implications on managing a high number of test engineers. And of course I don't know why and what is needed. It is my opinion from my perspective.
I didn't find an email, so I will post it here. Did you write "you're" on purpose on the first resolution?
ReplyDeleteI loved this post James and have also forwarded it to my team, you are one of the most outright person.
ReplyDeleteThis year I want to learn more and more, its always like that but this time I will follow a more structured regime. Majority of the times I do follow the 1 and 2 resolutions as mentioned by you but now I want to focus more on the 3 pointer. Please share your methods and approaches as well that you will be taking for minimizing the repetitive and wasteful testing being performed.
I think Google do a better job than most large technology firms when it comes to publicising known issues, although I guess there's always room for improvement.
ReplyDeleteI've not looked at ChromeOS but I've delved a little into the Chrome browser bugs and appreciated the input from the Chrome dev team.
Nice to see your user-focussed approach. I've always considered myself to be a user-centric tester (been doing mostly UAT-related testing throughout the last ten years). User experience can easily get pushed down the priority list when it should be right at the forefront
Getting testers to blog their experiences and collaborate on issues is an excellent resolution.
ReplyDeleteCarl
http://kungfutesting.blogspot.com/
I am really looking forward to read more about your testing practices this year. Great resolution!
ReplyDeleteAlthough you sound a bit like you want to emphasize some sort of disconnect between testers and developers. I am convinced that in healthy teams both roles are equally responsible to deliver quality. So, they want to work closely together, listen to each other, and have a sense for the problems the other role deals with.
I don't want to sound all touchy feely, my experience is just that some us vs. them does not help the user at all.
And yes, drive testing from the user's perspective! I could not agree stronger!
Looks great!
ReplyDeleteI am always wondering why companies like Google, Microsoft try to create the hybrid between tester and dev (SDET).
Why not a splitting the positions, at least in 3: dev that helps only testers, SDET and testers. Of course everyone should have the same skill but in different percentage.
I am a tester that focus on ET a lot so I don't know the implications on managing a high number of test engineers. And of course I don't know why and what is needed. It is my opinion from my perspective.
This is good article
ReplyDelete