RE: [Nant-users] nUnit2 task: Remove from project

[Tony_Bjerstedt]

I encountered a problem with the <nunit2> task not long ago. I went to the nUnit web site, downloaded the latest version (2.2.2), built and tested my code using it and VS. I then tried to run the tests using the <nunit2> task and they promptly failed.  As it turned out, the latest version of nUnuit is not supported by nAnt and that I should have been running a different version. (According to the mail thread when I asked about this, I was told that the recommend version is 2.1.4 [if I remember correctly] and that even the nUnit developers don't recommend the newer version.)   If other users have had similar experiences, I can understand where the <nunit2> task gets it's bad reputation. It only appears to work with selected versions of nUint.   Since some of the tests I wrote use features added in 2.2, I will either need to use <exec> or write my own custom task.   At a minimum (no matter where the task is located) the documentation should state, which versions of nUnit are supported. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank Striegel Sent: Tuesday, August 23, 2005 3:52 AM To: nant-users@lists.sourceforge.net Subject: AW: [Nant-users] nUnit2 task: Remove from project I'm using the NUnit2 task for more than a year without any problems.   Frank   -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Bart Read Gesendet: Montag, 22. August 2005 09:45 An: [EMAIL PROTECTED]; nant-users@lists.sourceforge.net Cc: Alan Wallace Betreff: RE: [Nant-users] nUnit2 task: Remove from project   I can see the point behind this, and to an extent I agree: if a feature is broken and there's no intention of fixing it then it should simply be removed, because otherwise people (like me - see my earlier post) are going to waste a lot of time trying to get something to work that just won't. But I have to be honest, and say that using <exec> is really a last resort. I'd pretty much rather write my own custom task than do this, especially if it's something that's going to be used by other people in the company. However, since many people are going to want to do at least some automated testing, and since this is something that should be encouraged (how tired are we all of using buggy software?), I really do think it's worth the effort of fixing NUnit2 for the 1.0 release.   Just my two-pence worth. To bring some balance to this though, and to be entirely fair, I should also point out that NAnt is a great piece of software that has made building our software a *lot* easier. We were using a commercial product before (naming no names), and to be honest there's just no comparison.   Thanks,     Bart     ====================== Bart Read Software Engineer Red Gate Software Ltd +44 (0) 870 160 0037 ext 31 ====================== From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 19 August 2005 00:25 To: nant-users@lists.sourceforge.net Subject: [Nant-users] nUnit2 task: Remove from project   To in-charge-type-dudes, There seems to be a lot of emails about the nUnit2 task not working properly. And generally the reply is a canned "nUnit2 task is not really supported. You are better off using <exec> and the nunit executable" For the 1.0 release, would it be an idea to remove the nUnit2 task? People are going to keep using it and striking problems unless either it is removed and they can only use <exec> or it is improved to be of releasable nature. I don't think it will matter how may faq entries, warnings, compiler warnings, etc, etc you put up. If someone sees an "nUnit2 task", and they are trying to implement nUnit testing they will jump on it. Angus. _______________________________ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.