Hi Sameer, CCNET makes no distinction between "build" and "test". All it does is run tasks (hence the "tasks" node), and it will report the statuses of those tasks. What do you mean by "My main aim is for CCNET to recognize it as a Test."?
If you are calling your batch file(s) from NAnt, you do not have to worry about writing your output as XML. The DOS output is wrapped by NAnt, and this will get reported to CCNET as XML. This is how I run many of my tasks. Regards, Ben On Jun 4, 2:04 pm, Sameer <[email protected]> wrote: > Thanks Alex. > > So for CCNET to identify a task as a test and NOT as part of the > build, the minimum requirement is to configure the test output as an > XSL sheet? > > In my final test output, I'll probably have only 2 or 3 lines of > messages. Do I still need to go through that process? OR is there an > alternative? > > Thanks, > Sameer > > On Jun 4, 12:49 pm, Alex <[email protected]> wrote: > > > > > It is possible to run them the way you describe. However, the output > > that you would merge in the publishers section needs to be XML. You > > then need an XSL sheet configured and present on both your web > > dashboard and build server to parse through the XML and display the > > relevant information. > > > On Jun 4, 1:45 pm, Sameer <[email protected]> wrote: > > > > Is it possible to run tests that I have included within a DOS batch > > > file (that calls other test .EXE files), through CCNET? My main aim is > > > for CCNET to recognize it as a Test. > > > > From what I've read, CCNET will identify it as a test if I generate an > > > output in XSL format and then merge it in the publishers section. Is > > > that correct? > > > > Currently, for my tests, I'm just using a NANT script that calls my > > > Batch file through <exec>. > > > > Thanks, > > > Sameer
