<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by bbcook</title>
    <description>Stories kicked by bbcook</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Configure log4net for Excel or LogParser friendly output</title>
      <description>log4net is a great logging framework, but parsing the output using standard tools can be difficult.

This handy article shows you a few tweaks you can make to your configuration so that your output can be read by most tools. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f11%2flog4net-logparser-excel-output.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f11%2flog4net-logparser-excel-output.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/tipsandtricks/Configure_log4net_for_Excel_or_LogParser_friendly_output</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/tipsandtricks/Configure_log4net_for_Excel_or_LogParser_friendly_output</guid>
      <pubDate>Sat, 22 Nov 2008 21:46:02 GMT</pubDate>
    </item>
    <item>
      <title>Legacy Projects: Test the User Interface with Selenium or WatiN</title>
      <description>Got a legacy project with no unit tests? Baffled where to start?

This is third in a series of posts that walk you through applying testing strategies to existing code. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f07%2ftest-presentation-layer-selenium-watin.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f07%2ftest-presentation-layer-selenium-watin.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Legacy_Projects_Test_the_User_Interface_with_Selenium_or_WatiN</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Legacy_Projects_Test_the_User_Interface_with_Selenium_or_WatiN</guid>
      <pubDate>Wed, 09 Jul 2008 04:33:43 GMT</pubDate>
    </item>
    <item>
      <title>Create Custom NUnit Categories</title>
      <description>Great walk through on how to use NUnit Categories for your project, as well as how to declare your category attributes.

Source code and compiled release available for your projects, too. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f06%2ftdd-custom-nunit-categories.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f06%2ftdd-custom-nunit-categories.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Create_Custom_NUnit_Categories</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Create_Custom_NUnit_Categories</guid>
      <pubDate>Wed, 18 Jun 2008 16:21:53 GMT</pubDate>
    </item>
    <item>
      <title>Test Driven Development Naming Conventions and Guidelines</title>
      <description>New TDD and experienced TDD developers will find this list of naming conventions and guidelines useful. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f06%2ftest-naming-conventions-guidelines.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f06%2ftest-naming-conventions-guidelines.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Test_Driven_Development_Naming_Conventions_and_Guidelines</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Test_Driven_Development_Naming_Conventions_and_Guidelines</guid>
      <pubDate>Thu, 05 Jun 2008 09:31:12 GMT</pubDate>
    </item>
    <item>
      <title>Test Driven Development Tips: Getting Value out of Code Coverage</title>
      <description>Lies, True lies and Statistics -- Coverage tools can be misleading.  So how does an organization benefit from having them?  Bryan provides some great field notes on do's and don'ts for code coverage, including how tests can ruin coverage. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f05%2ftdd-tips-getting-value-out-of-code.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fstupiddumbguy.blogspot.com%2f2008%2f05%2ftdd-tips-getting-value-out-of-code.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/unittesting/Test_Driven_Development_Tips_Getting_Value_out_of_Code_Coverage</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/unittesting/Test_Driven_Development_Tips_Getting_Value_out_of_Code_Coverage</guid>
      <pubDate>Tue, 20 May 2008 19:58:45 GMT</pubDate>
    </item>
  </channel>
</rss>