Comments on: Switching from MS Test to NUnit Testing http://dotnetchris.wordpress.com/2008/12/31/switching-from-ms-test-to-nunit-testing/ C# ASP.Net Development Weblog Wed, 28 Oct 2009 10:39:31 +0000 http://wordpress.com/ hourly 1 By: dotnetchris http://dotnetchris.wordpress.com/2008/12/31/switching-from-ms-test-to-nunit-testing/#comment-167 dotnetchris Sat, 03 Jan 2009 16:30:07 +0000 http://dotnetchris.wordpress.com/?p=182#comment-167 Khalid when you switch from MSTest to NUnit the ClassInitalize methods can't be static anymore. When they're created by MS Test by default they're marked static. I'm not sure if it matters to MS test if you remove static off it. I suppose you could do the precompiler directives to pick out which attributes syntax to use also. I'm not really sure how it'd be possible to mock the config files unless I actually put a layer on top of the configuration manager since this was about deploying like connectionstring.config and etc. Khalid when you switch from MSTest to NUnit the ClassInitalize methods can’t be static anymore. When they’re created by MS Test by default they’re marked static. I’m not sure if it matters to MS test if you remove static off it.

I suppose you could do the precompiler directives to pick out which attributes syntax to use also.

I’m not really sure how it’d be possible to mock the config files unless I actually put a layer on top of the configuration manager since this was about deploying like connectionstring.config and etc.

]]> By: Khalid Abuhakmeh http://dotnetchris.wordpress.com/2008/12/31/switching-from-ms-test-to-nunit-testing/#comment-166 Khalid Abuhakmeh Sat, 03 Jan 2009 16:15:07 +0000 http://dotnetchris.wordpress.com/?p=182#comment-166 I can't believe you had problems with MSTest and NUnit. I am able to jump seemlessly between the two frameworks in Team City and VS. They are the same exact tests. All I did was choose what syntax I wanted to go with and add some using statements at the top. #IF NUNIT using TestFixutreSetup = [mstest namespace].TestClassInitialize; #END IF and then add a new build in your environment. I'll create an example if you need me to. In terms of files, maybe you could abstract that away to an interface and mock it up. that way you are not subject to the structure of the file system. Yeah Nunit doesn't create folders, but MSTests does. I can’t believe you had problems with MSTest and NUnit. I am able to jump seemlessly between the two frameworks in Team City and VS. They are the same exact tests. All I did was choose what syntax I wanted to go with and add some using statements at the top.

#IF NUNIT
using TestFixutreSetup = [mstest namespace].TestClassInitialize;
#END IF

and then add a new build in your environment. I’ll create an example if you need me to.

In terms of files, maybe you could abstract that away to an interface and mock it up. that way you are not subject to the structure of the file system.

Yeah Nunit doesn’t create folders, but MSTests does.

]]>