Comments on: Getting a jump start on software test collaboration http://itknowledgeexchange.techtarget.com/software-quality/getting-a-jump-start-on-software-test-collaboration/ A SearchSoftwareQuality.com blog Sat, 28 Nov 2009 02:44:00 +0000 http://wordpress.org/?v=2.6.2 By: RobLambert http://itknowledgeexchange.techtarget.com/software-quality/getting-a-jump-start-on-software-test-collaboration/#comment-32 RobLambert Wed, 23 Sep 2009 16:27:42 +0000 http://itknowledgeexchange.techtarget.com/software-quality/?p=779#comment-32 You say you've never worked in an environment that doesn't allow for getting involved early. I've never worked in this environment either and most of my friends and peers have also never worked in this environment either. So does that environment exist? Or is it a convenient excuse? Or is it simply some testers don't know how to make their way in early? I liked the article but I tend to see that defects get raised in these informal/formal early testing sessions. They get found early. They get fixed immediately. They often don't get entered to the bug system. So the net effect I see is that the early involvers don't raise as many defects when entering their formal testing phase. The same goes when I get involved at a design stage. I can help the team to design out some of the defects I would riase when testing. Some are obvious, some not so. But being involved early allows you to air concerns and design decisions earlier meaning less chance of defects. It also allows you to lay down the types of things you'll be looking for when testing which often results in programmers unit testing for it, designers and BA including more detail in specs/stories etc and the testers being trusted for their honesty, critical eye and ease of working with. If only all testers could read this post of yours. It's a great post. Lots of insight. Rob.. http://thesocialtester.posterous.com/ You say you’ve never worked in an environment that doesn’t allow for getting involved early. I’ve never worked in this environment either and most of my friends and peers have also never worked in this environment either. So does that environment exist? Or is it a convenient excuse? Or is it simply some testers don’t know how to make their way in early?

I liked the article but I tend to see that defects get raised in these informal/formal early testing sessions. They get found early. They get fixed immediately. They often don’t get entered to the bug system. So the net effect I see is that the early involvers don’t raise as many defects when entering their formal testing phase.

The same goes when I get involved at a design stage. I can help the team to design out some of the defects I would riase when testing. Some are obvious, some not so. But being involved early allows you to air concerns and design decisions earlier meaning less chance of defects. It also allows you to lay down the types of things you’ll be looking for when testing which often results in programmers unit testing for it, designers and BA including more detail in specs/stories etc and the testers being trusted for their honesty, critical eye and ease of working with.

If only all testers could read this post of yours. It’s a great post. Lots of insight.

Rob..
 <a href="http://thesocialtester.posterous.com/" title="http://thesocialtester.posterous.com/" target="_blank">http://thesocialtester.posterous.com/</a>

]]>