<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx</link><description>I recently read an (internal, so I can't give a link, sorry) article by a developer pundit. In the article he opines that while the current practices of unit testing, etc. are having a definite impact on code quality, eventually we will reach a point</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>New Team System Stuff - 2004-11-19</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#267151</link><pubDate>Sat, 20 Nov 2004 07:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:267151</guid><dc:creator>Rob Caron's Blog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=267151" width="1" height="1"&gt;</description></item><item><title>re: Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#265959</link><pubDate>Thu, 18 Nov 2004 21:37:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:265959</guid><dc:creator>The Braidy Tester</dc:creator><description>As Jonathan says above, nobody is ever going to be as good at dreaming up good test case as a professional tester. (Sure, genius testers may show up occasionally on the customer team or other disciplines, but this will be few and far between.) Further, as we train our customers and developers to get good at one type of testing, there will always be a higher level for us to work to.&lt;br&gt;&lt;br&gt;Understanding the customer has always been part of being a good tester -- we just haven't consciously realized that in the past. Understanding the customer is the only way to build the product that will actually solve your customers' problems. If no one buys the product the product is going to die regardless how perfect it is.&lt;br&gt;&lt;br&gt;So yes, understanding the customer is good for developing the product and for keeping testers employed.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=265959" width="1" height="1"&gt;</description></item><item><title>re: Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#265728</link><pubDate>Thu, 18 Nov 2004 16:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:265728</guid><dc:creator>Futura</dc:creator><description>I agree with you that the role of a tester will be decided by the customer . Recently I worked on a XP project where manager prefer not to have the testers on the team. They have four customer support people who wrote acceptence test and also have the responsibility to interect with the customer. Devloper wrote the acceptance test using xUnit and test frameworks and one person is given the responsibility to run the regression suite. Since the customer people have clout and all the decision making power it basically tilt the balance in the team to their favour.Tech people (and test people) felt insecure as most of the decisions were routed through customer understanding people. &lt;br&gt;I think if the customer people develop the ability to write the test cases ( using scripting technique, which now a days so easy to learn) why a team would need a dedicated tester and for what purpose. Further XP and other new methodology is shifting the balance more toward customer understanding people, which is good for the business but is it good for developing a good product (and to keep tester employed) &lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=265728" width="1" height="1"&gt;</description></item><item><title>New Team System Stuff - 2004-11-17</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#258957</link><pubDate>Wed, 17 Nov 2004 20:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:258957</guid><dc:creator>Rob Caron's Blog</dc:creator><description>&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=258957" width="1" height="1"&gt;</description></item><item><title>re: the role of testers on agile projects</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#259093</link><pubDate>Wed, 17 Nov 2004 20:25:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:259093</guid><dc:creator>Jonathan Kohl</dc:creator><description>I've tested on a number of agile projects, and I don't see testers not being needed any time soon. It can be very different than testing on a more traditional waterfall kind of project, and I end up doing different tasks. It can be harder to find bugs, but I enjoy being able to try different things.&lt;br&gt;&lt;br&gt;One thing to note is that the testing described in XP and other agile practices can be very different from what conventional testers think of as &amp;quot;testing&amp;quot;. When developers are using TDD for example, the tests they are writing are more like examples that guide their work. Later on when they refactor, the tests are a kind of safety net that allows them to improve code with confidence. This is not what conventional testers do when they test. &lt;br&gt;&lt;br&gt;Customers find bugs, but this isn't their area of expertise. I've often worked as a testing coach with customers helping them develop tests, or running through acceptance tests with them. There can be large gaps between acceptance tests and the automated unit tests developed with xUnit tools during development. &lt;br&gt;&lt;br&gt;This is where a tester can fit on an agile project (among other places) - helping to identify these gaps. Testers are good at it, and I've yet to see a project yet that didn't benefit from the right kind of brain-engaged testing that tester folks can add to a project.&lt;br&gt;&lt;br&gt;Some agile projects do very well without conventional testers, and I've seen value added by having them. Ultimately, the question of whether there should be testers on agile projects will be answered by the customer. If they want testers on the team, they will need testers who know how to operate in that environment. &lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=259093" width="1" height="1"&gt;</description></item><item><title>re: Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#259003</link><pubDate>Wed, 17 Nov 2004 18:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:259003</guid><dc:creator>The Braidy Tester</dc:creator><description>The role of a tester on an agile project is a topic of great debate right now. I don't have any links handy but Googling for it should find bunches of opinions. Personally I'm glad to see the work Test is expected to do is finally approaching what I think our job should be: combining a great depth of understanding of the customer with a great depth of understanding of the application as a whole to do testing the app as a whole in a holistic way. &lt;br&gt;&lt;br&gt;Dev can do this to some extent, but they tend to be so deep into the innards of individual features that it's really hard for them to take a wider view. Test has been forced to live at this level as well because of the sheer number of bugs down there, but as Dev gets better at testing their own code we can widen our focus and spend more of our time taking that wider view.&lt;br&gt;&lt;br&gt;Testers will never be eliminated. Dev is never going to have the time to think about testing that we do. We can provide a huge service to Dev by helping them do better testing. We can provide a huge service to our customers by becoming an expert them and using that deep knowledge to drive our testing and to make our product truly useful to them. We can provide a huge service to ourselves by continually dreaming up better ways to do the testing we already know we need to do and figure out what testing we are missing.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=259003" width="1" height="1"&gt;</description></item><item><title>re: Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#258923</link><pubDate>Wed, 17 Nov 2004 17:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:258923</guid><dc:creator>Anon this time</dc:creator><description>There is no shortage of people who think others should collect and calculate stats.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=258923" width="1" height="1"&gt;</description></item><item><title>re: Software Statistics Engineer?</title><link>http://blogs.msdn.com/b/micahel/archive/2004/11/17/258881.aspx#258920</link><pubDate>Wed, 17 Nov 2004 17:04:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:258920</guid><dc:creator>Futura</dc:creator><description>Looks like the role of the future testers would be very limited. Current software development methodology emphasis alot on Dev to act as a tester. Will this means there will be vey few jobs for software testers in future. XP suggest that the customer people should write the acceptence test and dev should implement those as well as unit test. Agile process also emphasis on developer writing a test case. Does this means that testers would be eliminated. If not what their role would be?&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=258920" width="1" height="1"&gt;</description></item></channel></rss>