Developerslog.net

However it’s possible to test your WCF services using unit test by just referencing your service implementation (see Ploeh’s Blog) You gain a lot of benefit if you use the WCF infra structure to test your services.

For Example, did you ever get the error message during integration test (or worse, production) because your message couldn’t be serialized because of a null value. This wouldn’t happen if your unit test were using WCF. Espacially when you have large messages with a lot of elements.

See Howard’s blog how to implement this.

Curious why you unittest don’t log any messages using Log4Net? And you do have the configuration set in your app.config file? This is propably the result because your log4net config file isn’t deployed in the TestResult directory.

To enable Log4Net in your MSTest unittests :

• Add your Log4Net file to the deployment files
• Read the Log4Net configuration in your Assembly Initialize method (see below)

Add The Log4Net file to the deployment files

1. Double click on the LocalTestRun.testrunconfig File
2. Select deployment items
3. Click Add
4. Browse to your Log4Net config file.
   (This can be the same file as in your web or Windows project. In this way you use the same configuration as in your normal project.)

Reading Log4Net configuration
You can read the Log4Net configuration in you class initialization method but then you will have to put this information in every unittest class in you assembly. A better way is to put this code in the AssemblyInitialize method. The AssemblyInitialize method is just like the ClassInitialize method but this method will be executed only once before the execution of the unittest in your assembly.

Create a new class, for example TestAssemblyInit.cs and add the code below

[AssemblyInitialize()]
public static void MyTestInitialize(TestContext testContext)
{
// Take care the log4net.config file is added to the deployment files of the testconfig
FileInfo fileInfo;
string fullPath = Path.Combine(System.Environment.CurrentDirectory, "log4net.config");
fileInfo = new FileInfo(fullPath);

// test to see if it works
Log.Info("check");
}