That's what CruiseControl does with ant, it's a servlet based solution that runs JUnit tests automatically.
The left frame as the day/hours of every build, the right frame as the executive report. It's a tree that branches in failure/success. It then branches on the different Test suite and the different test Cases. You click on one of the test to go to the full view. Any solution that allows you to view 1000+ test cases is a good solution :) Phil PS Not that I have that many test cases, but one day... > -----Original Message----- > From: Scott Hernandez [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 03, 2002 12:09 PM > To: 'Tomas Restrepo'; 'NantDev' > Subject: RE: [nant-dev] New NUnitReport look? > > > Yep, that sounds good. > > Maybe it could put the successful tests in a comma sep. list so that > vertical space is not used so much. You could break the report down by > success/failure so it would be easier to scan for failures. Then these > sections could be collapsible. Maybe the success section would be > collapsed by default. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:nant-developers- > > [EMAIL PROTECTED]] On Behalf Of Tomas Restrepo > > Sent: Monday, June 03, 2002 9:03 AM > > To: NantDev > > Subject: Re: [nant-dev] New NUnitReport look? > > > > Phillip, > > > > > Perhaps it would be a good idea to split it in two files. One that > > contains the > > > "executive summary", i.e. something you'd give to a > program manager. > The > > other > > > would be something like you have, it contains everything > you need to > > know > > in a > > > readable format so that as a dev, it's easy to get to the > fun part, > fix > > stuff and shit. > > > > > > That sounds like an interesting idea... who else would be interested > in > > such > > a report? > > > > What information would you think such an executive summary should > have? > > > > Another idea I'm thinking about is adding a "onlyerrors" > attribute to > the > > nunitreport task that would cause it only to include failed tests in > the > > report, such that no detail on sucessful test methods was included. > That > > by > > itself could significantly reduce the report size while still being > very > > useful, imho... > > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
