General

Requirements

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?

Dialogs automated and asserts rudimentary only on dialogs
- With database and server
  - reset database and Import Data through nant
    - Import/Export Gift batches
    - GL Tests
  - generates data through GUI with minimal random string
    - GL Forms
  - Expects certain data exists / does not exists
    - MFinance.server.gift
    - Partner import (assert on the number of imported partners only)
A first concept of some dialog tester classes which can be generated automatically by the yaml files

Sit down and think, what functionality you have implemented
Write down, what needs to be tested. There are always following cases:
1. Good case in middle range of the possible values
2. Good case next to the limits of the possible values in all directions
3. Bad Case in middle range of the not allowed values
4. Bad Case next to the limits of the not allowed values
Write down, on what outcome you should assert (Remember: We are doing white box tests and look INTO the software!)
1. in the database
2. in the state of the server (if in the same process)
3. in the state of the client (if client is used)
Write down, which test data you need and how you could generate it
Implement the test. Do the test in three stages:
Testing through Client GUI should be avoided, if possible. It is better to change the client, so that this is possible

Always ensure, that you on later stages you do not re-test earlier stages. Sometimes it is sufficient to show, that the function is correctly called!
1. Test without DB, whenever possible
2. Test inside the server process
3. Test like a client without GUI
Get your test working

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)
- Mirror concept (Interface to reflection for accessing private properties and methods)
- http://stackoverflow.com/questions/3678783/mbunit-vs-nunit
- http://stackoverflow.com/questions/261139/nunit-vs-mbunit-vs-mstest-vs-xunit-net
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)