<?xml version="1.0" encoding="ISO-8859-1"?><!-- OPML generated by OPML Editor v10.1a8 on Wed, 30 Jun 2010 15:31:08 GMT -->
<opml version="2.0">	<head>		<title>lo</title>		<dateCreated>Wed, 30 Jun 2010 15:31:06 GMT</dateCreated>		<dateModified>Wed, 30 Jun 2010 15:31:07 GMT</dateModified>		<ownerName>Dave Winer (Larry King)</ownerName>		<ownerEmail>dave.winer@gmail.com</ownerEmail>		<expansionState>1</expansionState>		<vertScrollState>1</vertScrollState>		<windowTop>194</windowTop>		<windowLeft>815</windowLeft>		<windowBottom>900</windowBottom>		<windowRight>1686</windowRight>		</head>	<body>		<outline text="Writing good bug reports" created="Wed, 30 Jun 2010 12:01:43 GMT" ctSaves="7" flPreview="false" storySerialNum="304" text="Writing good bug reports" type="scripting2Post" url="http://scripting.com/stories/2010/06/30/writingGoodBugReports.html" whenLastSave="Wed, 30 Jun 2010 12:31:02 GMT">			<outline text="&lt;img src=&quot;http://images.scripting.com/archiveScriptingCom/2010/06/30/sneakers.jpg&quot; width=&quot;145&quot; height=&quot;154&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named sneakers.jpg&quot;&gt;The other day I wrote about the &lt;a href=&quot;http://scripting.com/stories/2010/06/27/howToApproachAnAlphaProduc.html&quot;&gt;Zen of being a tester&lt;/a&gt; of a new piece of software. Be patient. It's a long journey. The bugs are there for a reason, it's best to assume they will always be there then you will be surprised and delighted in the unlikely event that one of them goes away. " created="Wed, 30 Jun 2010 11:46:37 GMT" pgfnum="186"/>			<outline text="Today we get a little bit more pragmatic. " created="Wed, 30 Jun 2010 11:48:11 GMT" pgfnum="187"/>			<outline text="You've been asked to test the software because the people who are writing it would like your help to make it better. They want to fix bugs, and the easier you make it for them, the more likely it is they will be able to. Sometimes people produce bug reports that are so insightful they lead the programmer right to the mistake in the code." created="Wed, 30 Jun 2010 11:48:25 GMT" pgfnum="188"/>			<outline text="The basic information a bug report should contain is this: " created="Wed, 30 Jun 2010 11:49:21 GMT" pgfnum="189"/>			<outline text="1. What you were doing. " created="Wed, 30 Jun 2010 11:58:19 GMT" pgfnum="196"/>			<outline text="2. What you expected to happen. " created="Wed, 30 Jun 2010 11:58:26 GMT" pgfnum="199"/>			<outline text="3. What actually happened." created="Wed, 30 Jun 2010 11:58:31 GMT" pgfnum="200"/>			<outline text="All three parts are very important. If you really did discover a bug, the programmer will need to know what you were doing so he or she can try to reproduce it. If they can't, it will be next to impossible to fix it. " created="Wed, 30 Jun 2010 11:49:44 GMT" pgfnum="190"/>			<outline text="The second part helps nail down the first part. Usually people know what they were expecting. Also, it's possible that what you were expecting isn't what the software does. An extreme example: &quot;I was expecting that when I pressed the blue button at the bottom of the screen I would be granted three wishes.&quot; " created="Wed, 30 Jun 2010 11:51:14 GMT" pgfnum="191"/>			<outline text="For the third part a screen shot can help. It may contain information that's meaningful to the programmer that you wouldn't think to include in your report." created="Wed, 30 Jun 2010 11:52:51 GMT" pgfnum="192"/>			<outline text="Another way to help the programmer is to say if the problem is or isn't reproducible. That is, if you try step #1 again, do you get the results in step #3? By trying to reproduce it you may add important information to the first part of the report." created="Wed, 30 Jun 2010 11:54:13 GMT" pgfnum="193"/>			<outline text="PS: All bugs are reproducible, that's almost the definition of a bug." created="Wed, 30 Jun 2010 11:55:39 GMT" pgfnum="194"/>			<outline text="PPS: Another &lt;a href=&quot;http://www.chiark.greenend.org.uk/~sgtatham/bugs.html&quot;&gt;howto&lt;/a&gt; re bug reports." created="Wed, 30 Jun 2010 15:30:46 GMT" pgfnum="202"/>			</outline>		</body>	</opml>