Bryan, I don't know if this will be appropriate, but you might want to consider the mechanism used by CruiseControl.NET. (CCNet itself would probably be even better, since you could end up with a little icon on each developers machine letting you know if the build is good or bad. One user even has CCNet turning on a lava lamp when the build fails [Their goal - to fix the build before the lava starts bubbling!], but I suspect that implementing anything so advanced would be an uphill struggle as you describe).
The mechanism used is to apply a style sheet to the XML output from NUnit-Console. If you still wanted the "eyeball from across the room" approach, the formatted output could be displayed using Internet Explorer. For more information about CCNet, see the website at http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+Cruis eControl.NET If you haven't seen it in action, the CCNet team "eat their own dog food". A live version of the CCNet server can be found at http://ccnetlive.thoughtworks.com/ccnet/, A sample of the interpreted NUnit output I mention can be found at http://ccnetlive.thoughtworks.com/ccnet/default.aspx?_action_NUnitDetail sBuildReport=true&server=local&project=CCNet&build=log20060310095601Lbui ld.1.1.0.2230.xml (or more simply by clicking the "NUnit Details" choice for a particular build. I personally find the CCTray utility (see http://confluence.public.thoughtworks.org/display/CCNET/CCTray for more details) to be very helpful. It would also allow developers to start a build, and monitor the current build pass/fail status without having to leave their desk. If I were you, I would also be asking myself if I really want to work for your company. Unit testing and continuous integration are so much a part of best practices that any company unwilling to accept them is (IMHO) extremely unlikely to consistently deliver a quality product. For me, those two things are almost as important as source code control, and a bug tracking database. Hope you find a solution that works well for you. Regards, Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bryan White Sent: Monday, March 13, 2006 18:31 To: [email protected] Subject: RE: [NAnt-users] Help on Integrating Nant with Nunit gary wrote: > ... > Why are you running the NUnit GUI from within NAnt? Does this even > work if you're building via a scheduled task, CruiseControl.Net, or > other batch mechanism with no display? > > For running from NAnt, I'd use the NUnit console, or better yet, the > NUnit2 task, as indicated in my previous note. > > Gary Umm, IWFM! Could our build file be improved and still do what's wanted? Maybe, but read on. We have a dedicated Windows build machine shared by several developers. After any checkin, that developer is responsible that the build isn't broken, which is demonstrated by running Unit Tests (kicked off by manually running a batch file). The successful build (or otherwise) is easy to check by using good old Mark One Eyeball from across the office. No emails, no log browsing. Okay, maybe it's not the best way and won't work for everyone, but it's the way that we've developed our build process. It was an uphill struggle getting Unit Tests accepted as part of the development process, and I'm still unsuccessful in trying to get multiple checkouts allowed. Some people here are rather blinkered, so anything too drastic or different from a manual, time and labour intensive process is doomed to failure. Despairingly Bryan White "Brewmanz" ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ NAnt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ NAnt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
