Hi Gert, > If I recall correctly, the NUNit Team (Charlie Poolie, that > is lol) advises users to stick with 2.2.0.
Yup. That said, we test NUnit itself using NANT by running nunit-console with the <exec> task. > I think they consider the 2.2.1 and 2.2.2 releases as unstable. Yes, in the sense that the features and interfaces may change in the future. So, while one could make the NUnit2 task work with 2.2.2, you'd probably end up changing it again for 2.2.3. > > Should I give up on <nunit2> and use <exec> instead? > > I might consider rewriting the <nunit2> task as a wrapper for > the nunit-console command line tool. > > But in my opinion, NUNit lacks support for specifiying a list > of referenced assemblies (that get loaded into the test > domain, but are not scanned for testfixtures). > > Charlie, any chance this might make it into a future revision > of NUNit or is this already supported (and did I overlook somehow) ? Can you explain further what you might want here? In general, we rely on the normal loading of referenced assemblies. There is a way to include a list of non-test assemblies in an nunit project however. Regarding wrapping nunit-console, I think that's not as good an idea as our working toward an interface that does everything that's needed to run NUnit tests programmatically. That way, nunit-console can continue to evolve. BTW, the current code loads old versions of NUnit without any issue. We should be able to leverage that in some way. Charlie ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
