Hi Thibaut thanks for that. While CruiseControl and automated testing are some way off on our radar, I hope to find the time to investigate them, especially the latter. In that respect, I would appreciate if you could possible provide a small sample build file outlining the structure required to carry out the tasks you mention below - especially Nunit testfixtures, fxcop, ndoc, ncover.
Cheers, Mauro Ciaccio P.S. Curtis, thanks again for the feedback > -----Original Message----- > From: Thibaut Barrère [mailto:[EMAIL PROTECTED] > Sent: 17 December 2004 12:34 > To: [EMAIL PROTECTED] > Cc: NAnt Users mailing list > Subject: Re: [Nant-users] Using Nant on Test Servers > > > Hi Mauro, > > We're also using NAnt and CruiseControl to automate the full cycle. > > We have a single NAnt build script to : > - compile (debug/release) the .net solutions and associated tests > - run the unit tests and acceptance tests (both in the form of NUnit > testfixtures), invalidating the build on failure > - check the test coverage (ncover), check best practices (fxcop) > - generate the documentation (ndoc) > - increment version numbers > - publish to a common binary repository (à-la-Maven) > > > a) Does "drop the test itself into Nant" mean that our QA staff need to > > create test scripts in Nant? Or is there some way to > > run 3rd party software scripts from within Nant? > > Not necessarily. You can have QA (for acceptance testing )or > developers (for unit testing ) write tests in the form of NUnit tests > in C# or other .Net languages (as NUnit is directly supported by > NAnt), or instead run third party software using either the Exec task > or by writing a custom NAnt task (quite easy as well; we've done this > to publish the binaries and documentation to a network drive for > instance). > > > b) Could you explain a bit what CruiseControl is used for > and/or provide a > > link? > > CruiseControl is a continuous integration server. Basically it allows > you to setup automated build, either periodically or when checkins are > detected in your VCM. > > On such triggers the source code get updated to the latest version > from the VCM, then CruiseControl allows to launch automatically a NAnt > script. As a simple but less powerful alternative you can build a > VS.Net solution directly with devenv.exe. > > It natively supports NUnit and publish the reports of unit tests > through a website. The developers are kept aware of the state of the > build (successful/broken) either by a system tray icon, a web site, > emails or other kind of "publishers". > > You can have a look here for more information : > - http://confluence.public.thoughtworks.org/display/CCNET/Welcome%2Bto%2BCruis eControl.NET - and the overview diagram here! : http://confluence.public.thoughtworks.org/display/CCNET/CruiseControl.NET+In tegration+Process cheers Thibaut Barrère ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
