Unit Testing on Marko Apfel

LINQ and ArcObjects

Wed, 12 Sep 2012 15:20:00 +0200

Motivation

LINQ (language integrated query) is a component of the Microsoft. NET Framework since version 3.5. It allows a SQL-like query to various data sources such as SQL, XML etc.

Like SQL also LINQ to SQL provides a declarative notation of problem solving – i.e. you don’t need describe in detail how a task could be solved, you describe what to be solved at all. This frees the developer from error-prone iterator constructs.

xUnit runner eats system diagnostic output

Mon, 07 Nov 2011 13:28:00 +0100

Problem

When using xUnit and constructs like Debug.WriteLine the DbgView-tool does not show the written output anymore.

Solution

Add a new Listener – for example:

Debug.Listeners.Add(new DefaultTraceListener());

InternalsVisibleTo, PublicKey and PublicKeyToken

Thu, 27 Oct 2011 14:35:00 +0200

Intro

If you want to test the internals of a productive assembly you must mark the assembly with the InternalsVisibleTo-attribute. This attribute has only one constructor which needs the name of the testing assembly.

Let ReSharper and xUnit work together

Sun, 05 Jun 2011 13:41:00 +0200

Getting the ressources

First at all download

xUnit
xUnit Contrib ReSharper
This gives you a bridge between ReSharper functionality and your XUnit coding.

Installation und Configuration

Unzip both archives.

xUnit part

Configure the code to use xUnit

Normally I prefer a single checkout point for my developing solution – this whole bundle I name DevTree. One of the top folders in the hierarchy of this DevTree is a lib-Folder. Beneath this folder all of the 3rd party libs which I use in my solution are located – all of them in an own folder. So I copy xunit.dll to a folder <DevTree-Root>\lib\xUnit.

Code Contracts: For unit test a manual rebuild is needed for toggeling “runtime checking”

Sat, 04 Jun 2011 01:19:00 +0200

Toggeling the checkbox Perform Runtime Contract Checking lets run the next application start with the new set option. But for unit test an explicit new build will apply the option for the next run.

Set ApartmentState for ArcObjects-logic in separate threads

Wed, 08 Sep 2010 10:54:00 +0200

Problem context

We use a backgroundworker to load .MXD documents from several places of the system and extract meta data and thumbnails which a GUI component shows in an asynchronous way.

The unit tests for this logic throws an exception during the access the thumbnail:

Interpretations of F.I.R.S.T.

Mon, 19 Jul 2010 14:49:00 +0200

Fast
Many per second
Independent
Ability to to run test cases in any order
Isolated
only one aspect per test case –> Failure reasons could better be identified
Repeatable
Execution order does no matter
Self-validating
No manual evaluation required
Small
Easy to understand, evolvable
Transparent
purpose of test case should be clear
Timely
Written before/during code

Integrate NUnit in Hudson CI-server

Wed, 07 Jul 2010 15:41:00 +0200

Precondition

Naming

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.

NUnit project file cant reference assemblies which are not in subfolders

Fri, 12 Jun 2009 13:35:00 +0200

We use a developer tree like

src (contains the master-SLN and other code-stuff)
build (contains tools to build assemblies, code-doku, ..)
bin (central common output-folder for c#-compiler)

Under src normally the <project>.nunit should lay. But this file then references the assembly in a schema like: <assembly path="..\bin\Debug\EsriDE.PipelineManagement.Core.ClassExtensions.Test.dll" >