<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NUnit on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/nunit/</link><description>Recent content in NUnit on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 02 Aug 2011 10:49:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/nunit/index.xml" rel="self" type="application/rss+xml"/><item><title>Performance-Analyzing of log4net regarding creation of new logger vs. taking an existing one</title><link>http://blog.marko-apfel.de/posts/performance-analyzing-of-log4net-regarding-creation-of-new-logger-vs-taking-an-existing-one/</link><pubDate>Tue, 02 Aug 2011 10:49:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/performance-analyzing-of-log4net-regarding-creation-of-new-logger-vs-taking-an-existing-one/</guid><description>&lt;h2 id="motivation"&gt;Motivation&lt;/h2&gt;
&lt;p&gt;During playing with AOP framework PostSharp I thought about the technique to weave the logger instances inside the code by using the CompileTimeInitialize–method. Unfortunately my logging-stuff must be serializable. This is not given. So I must use the other weaving point and access my Loggers.&lt;/p&gt;</description></item><item><title>Integrate NUnit in Hudson CI-server</title><link>http://blog.marko-apfel.de/posts/integrate-nunit-in-hudson-ci-server/</link><pubDate>Wed, 07 Jul 2010 15:41:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/integrate-nunit-in-hudson-ci-server/</guid><description>&lt;h2 id="precondition"&gt;Precondition&lt;/h2&gt;
&lt;h3 id="naming"&gt;Naming&lt;/h3&gt;
&lt;p&gt;Its a good practice to have a common naming schema for test projects, fixture categories and fixture. Especially to configure automatic runs of unit tests is much more easier with this.&lt;/p&gt;</description></item><item><title>NUnit project file cant reference assemblies which are not in subfolders</title><link>http://blog.marko-apfel.de/posts/nunit-project-file-cant-reference-assemblies-which-are-not-in-subfolders/</link><pubDate>Fri, 12 Jun 2009 13:35:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/nunit-project-file-cant-reference-assemblies-which-are-not-in-subfolders/</guid><description>&lt;p&gt;We use a developer tree like&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;src&lt;/code&gt; (contains the master-SLN and other code-stuff)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;build&lt;/code&gt; (contains tools to build assemblies, code-doku, ..)&lt;/li&gt;
&lt;li&gt;&lt;code&gt;bin&lt;/code&gt; (central common output-folder for c#-compiler)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Under src normally the &lt;code&gt;&amp;lt;project&amp;gt;.nunit&lt;/code&gt; should lay. But this file then references the assembly in a schema like:
&lt;code&gt;&amp;lt;assembly path=&amp;quot;..\bin\Debug\EsriDE.PipelineManagement.Core.ClassExtensions.Test.dll&amp;quot; &amp;gt;&lt;/code&gt;&lt;/p&gt;</description></item></channel></rss>