<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: The trap of not asking questions</title>
	<atom:link href="http://testingpodcast.com/the-trap-of-not-asking-questions/feed/" rel="self" type="application/rss+xml" />
	<link>http://testingpodcast.com/the-trap-of-not-asking-questions/</link>
	<description>Audio podcasts on software testing. All of them.</description>
	<lastBuildDate>Thu, 03 May 2012 19:06:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Prasad</title>
		<link>http://testingpodcast.com/the-trap-of-not-asking-questions/comment-page-1/#comment-5831</link>
		<dc:creator>Prasad</dc:creator>
		<pubDate>Sun, 18 Dec 2011 06:25:19 +0000</pubDate>
		<guid isPermaLink="false">http://testingpodcast.com/?p=220#comment-5831</guid>
		<description>There are some projects wherein I have experienced that the developers dont like to answer questions as they are very busy and sometimes they do not know the complete functionality, Also there&#039;s no proper documentation and the users are not available.  This puts a fear in the minds of testers, and they start testing based on certain assumptions which may not be right.
Developing a relationship with the developers is one way to do it but how do you deal with developers who keep complaining on your  back once you ask questions?</description>
		<content:encoded><![CDATA[<p>There are some projects wherein I have experienced that the developers dont like to answer questions as they are very busy and sometimes they do not know the complete functionality, Also there&#8217;s no proper documentation and the users are not available.  This puts a fear in the minds of testers, and they start testing based on certain assumptions which may not be right.<br />
Developing a relationship with the developers is one way to do it but how do you deal with developers who keep complaining on your  back once you ask questions?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

