<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Sam w/o Max</title>
	<atom:link href="http://gameqablog.com/2006/11/sam-wo-max.html/feed" rel="self" type="application/rss+xml" />
	<link>http://gameqablog.com/2006/11/sam-wo-max.html</link>
	<description>And you thought your Quality Assurance staff were illiterate</description>
	<pubDate>Fri, 21 Nov 2008 10:14:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Sam Kalman</title>
		<link>http://gameqablog.com/2006/11/sam-wo-max.html#comment-50</link>
		<dc:creator>Sam Kalman</dc:creator>
		<pubDate>Thu, 09 Nov 2006 17:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://gameqablog.com/wp/?p=41#comment-50</guid>
		<description>Hey Zach, thanks for the links!  I hear your reservations about SBT &#038; repro steps.  One of the tricky balances of SBT is deciding the amount of time you spend testing versus the amount of time you spend reproducing bugs.  The amount of time in each category is tracked as a key metric, so if you do end up spending a lot of time trying to get two grunts fall into each other, your lead/dev/management will know that.&lt;br/&gt;&lt;br/&gt;However, I should point out that SBT in no way promotes bad repro steps.  Regardless of the time you spend in-session before finding a bug, the write-up should always be isolated.  Especially for a bug like this one, which is really independent of location.  Identifying and supplying good repro steps is really a separate skill from running Session-Based Testing.&lt;br/&gt;&lt;br/&gt;Plus, I love your post title L.O.L.</description>
		<content:encoded><![CDATA[<p>Hey Zach, thanks for the links!  I hear your reservations about SBT &#038; repro steps.  One of the tricky balances of SBT is deciding the amount of time you spend testing versus the amount of time you spend reproducing bugs.  The amount of time in each category is tracked as a key metric, so if you do end up spending a lot of time trying to get two grunts fall into each other, your lead/dev/management will know that.</p>
<p>However, I should point out that SBT in no way promotes bad repro steps.  Regardless of the time you spend in-session before finding a bug, the write-up should always be isolated.  Especially for a bug like this one, which is really independent of location.  Identifying and supplying good repro steps is really a separate skill from running Session-Based Testing.</p>
<p>Plus, I love your post title L.O.L.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
