<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Is document a dirty word in Exploratory Testing?</title>
	<atom:link href="http://mavericktester.com/is-document-a-dirty-word-in-exploratory-testing/feed" rel="self" type="application/rss+xml" />
	<link>http://mavericktester.com/is-document-a-dirty-word-in-exploratory-testing</link>
	<description>The startup&#039;s software tester</description>
	<lastBuildDate>Tue, 13 Jul 2010 23:47:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Kelly</title>
		<link>http://mavericktester.com/is-document-a-dirty-word-in-exploratory-testing#comment-588</link>
		<dc:creator>Michael Kelly</dc:creator>
		<pubDate>Mon, 06 Apr 2009 19:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.testingtimes.com.au/?p=34#comment-588</guid>
		<description>I recently wrote an &lt;a href=&quot;http://www.informit.com/articles/article.aspx?p=1325263&quot; rel=&quot;nofollow&quot;&gt;article&lt;/a&gt; on documentation, and as I was writing it I found that I do more documentation then I thought I did. As also realize that my current testing team does WAY more high-value documentation in the form of charters and session notes than I&#039;ve seen at most companies I&#039;ve worked at. My current team writes up a lot, but it&#039;s all new information (very little opportunity for copy and paste) and it&#039;s all focused on solving problems or creating opportunities for tester feedback.</description>
		<content:encoded><![CDATA[<p>I recently wrote an <a href="http://www.informit.com/articles/article.aspx?p=1325263" rel="nofollow">article</a> on documentation, and as I was writing it I found that I do more documentation then I thought I did. As also realize that my current testing team does WAY more high-value documentation in the form of charters and session notes than I&#8217;ve seen at most companies I&#8217;ve worked at. My current team writes up a lot, but it&#8217;s all new information (very little opportunity for copy and paste) and it&#8217;s all focused on solving problems or creating opportunities for tester feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Estella Moreno</title>
		<link>http://mavericktester.com/is-document-a-dirty-word-in-exploratory-testing#comment-560</link>
		<dc:creator>Estella Moreno</dc:creator>
		<pubDate>Sat, 10 Jan 2009 02:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.testingtimes.com.au/?p=34#comment-560</guid>
		<description>hi
asgkyr5xs4xf5ke9
good luck</description>
		<content:encoded><![CDATA[<p>hi<br />
asgkyr5xs4xf5ke9<br />
good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne-Marie</title>
		<link>http://mavericktester.com/is-document-a-dirty-word-in-exploratory-testing#comment-503</link>
		<dc:creator>Anne-Marie</dc:creator>
		<pubDate>Wed, 02 Jul 2008 04:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blog.testingtimes.com.au/?p=34#comment-503</guid>
		<description>Thanks for your comment Venkat, though I believe that the context of what you&#039;re testing is not just limited to the end user but depends on what your stakeholder’s are looking for. 
For example, the context of the testing may be its compliance to a standard etc.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment Venkat, though I believe that the context of what you&#8217;re testing is not just limited to the end user but depends on what your stakeholder’s are looking for.<br />
For example, the context of the testing may be its compliance to a standard etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
