From: Charlie P. <ch...@po...> - 2007-11-09 14:29:05
|
Hi Steve, I'm quite surprised that there is a dependecy at all - you'd think I'd know, but I didn't. Is this purely on the basis of how failures are reported, or is it deeper than that? Charlie _____ From: nmo...@li... [mailto:nmo...@li...] On Behalf Of Steve Mitcham Sent: Thursday, November 08, 2007 12:16 PM To: NMock2 Development Discussion Subject: [NMock2-Dev] NUnit vs. MbUnit I'm in the good position of having gotten my company to adopt NMock2 into the development process, and to get the permission needed to work on the OSS side and re-post our changes to the community. I've been harping on the need to 'play nice' with the communities providing us all of our test harness stuff recently. Anyway, currently there is a desire to convert our internal copy of NMock2 to use MbUnit as the testing framework instead of NUnit. They have to certify the functionality of all the development tools and they already have what they need for MbUnit so they want to use it for the test suite. I'm maintaining parallel trees to map the internal version and the external versions together. We have some versioning requirements that I don't want to leverage on the main development branch of NMock so I keep it separate. While I am of the mind of 'if it isn't broken, don't fix it', I have to do the work anyway, so. Would anyone be interested in the move to MbUnit or should I just keep it internal. Again, I'm not suggesting it, just trying to get a feel for whether anyone wants it. |