<?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: 10 steps on how to report bugs</title>
	<atom:link href="http://www.webanalyticsbook.com/offtopic/how-to-report-bugs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webanalyticsbook.com/offtopic/how-to-report-bugs/</link>
	<description>Daily webanalytics news</description>
	<pubDate>Mon, 01 Dec 2008 19:34:19 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: admin</title>
		<link>http://www.webanalyticsbook.com/offtopic/how-to-report-bugs/#comment-6242</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 03 Oct 2007 01:49:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/archives/1018#comment-6242</guid>
		<description>Agree! All the points you mention above are true.  A video is actually a great idea. Thanks for the input!</description>
		<content:encoded><![CDATA[<p>Agree! All the points you mention above are true.  A video is actually a great idea. Thanks for the input!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vittorio</title>
		<link>http://www.webanalyticsbook.com/offtopic/how-to-report-bugs/#comment-6240</link>
		<dc:creator>Vittorio</dc:creator>
		<pubDate>Tue, 02 Oct 2007 23:49:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/archives/1018#comment-6240</guid>
		<description>Great tutorial.

Sometimes, it takes less time to record a short video of you reproducing the bug rather than taking several screenshots. I use Camtasia to do that and it is a real time saver.

Also, if we are dealing with web applications, it is nice to ask our developers to include a custom error page that automatically sends an email to the developer every time there's a bug, usually with the line of code that causes the problem, etc.

And for client-side applications, a log file is of great help to the developer that needs to find out what caused the bug.</description>
		<content:encoded><![CDATA[<p>Great tutorial.</p>
<p>Sometimes, it takes less time to record a short video of you reproducing the bug rather than taking several screenshots. I use Camtasia to do that and it is a real time saver.</p>
<p>Also, if we are dealing with web applications, it is nice to ask our developers to include a custom error page that automatically sends an email to the developer every time there&#8217;s a bug, usually with the line of code that causes the problem, etc.</p>
<p>And for client-side applications, a log file is of great help to the developer that needs to find out what caused the bug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S.Hamel</title>
		<link>http://www.webanalyticsbook.com/offtopic/how-to-report-bugs/#comment-6232</link>
		<dc:creator>S.Hamel</dc:creator>
		<pubDate>Tue, 02 Oct 2007 16:58:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.webanalyticsbook.com/archives/1018#comment-6232</guid>
		<description>Good post! At point 2, you should stress out that it's not only describing the bug ("I got an error saying this &#38; that") but the steps that led to the problem ("I came on the site from Google search XYZ, clicked on the promo item, and when I tried to do the checkout I got error this &#38; that"). Give as much detail as possible about the clicks and the values put in forms at each step of your visit. When describing a problem, avoid stating what "you" think is the issue and focus on facts.

Stephane Hamel
http://blog.immeria.net</description>
		<content:encoded><![CDATA[<p>Good post! At point 2, you should stress out that it&#8217;s not only describing the bug (&#8221;I got an error saying this &amp; that&#8221;) but the steps that led to the problem (&#8221;I came on the site from Google search XYZ, clicked on the promo item, and when I tried to do the checkout I got error this &amp; that&#8221;). Give as much detail as possible about the clicks and the values put in forms at each step of your visit. When describing a problem, avoid stating what &#8220;you&#8221; think is the issue and focus on facts.</p>
<p>Stephane Hamel<br />
<a href="http://blog.immeria.net" >http://blog.immeria.net</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
