General

How do we want to get test peripherals?

Write test data into database
- Set up new, additional test data for each test run
- Delete database and set up a database snapshot
Write mock ups, so that database is not needed for the test
Mixed way of test data in database and mock up

Intuitive feeling: Test data in database by adding test data for each test run, perhaps mixed with some mock ups

Tests, which are testing the server code
- by calling the server functionality directly (in the same process)
- by connecting as client to the server
Tests, the client code without UI
Tests, which are testing by interacting with the UI?

http://www.nunit.org/
- ChristianK uses the version of NUnit that is integrated in SharpDevelop 3.2, as well as the standalone NUnit application. The SharpDevelop-bundled version works well and is nicely integrated into the IDE, but doesn't offer the full feature set of the standalone NUnit application. Combined with the integrated NCover application it is very handy, though!
  - Caveat: The test project needs to be a Commandline or Windows Form Project for it to work (DLL projects don't work).
http://gallio.org/ ( http://www.mbunit.com/ is part of it)
http://www.csunit.org/
http://dotunit.sourceforge.net/
https://launchpad.net/nunit-3.0/ (Still beta version)
http://xunit.codeplex.com/

http://ncover.sourceforge.net/
- ChristianK uses the version of NCover that is integrated in SharpDevelop 3.2. It works well and is nicely integrated. Combined with the integrated NUnit application it is very handy!
  - Caveat: The test project needs to be a Commandline or Windows Form Project for it to work (DLL projects don't work).
http://nester.sourceforge.net/

http://code.google.com/p/autofac/ (Library for Inversion of Control / Dependency Injection)
http://roaster.codeplex.com/ (nunit for compact framework)
http://dbunit-net.sourceforge.net/ (Write data to database and remove it afterwards)
http://nbehave.org/ (Write test in almost human English language and map the steps to C# classes)