Also in the ant javadocs it says something like: "If you want to use Xalan 1.2.2, the noframes report is still supposed to work. If you want the frames support, copy the file junit-frames-xalan1.xsl from the Ant distribution's etc directory to a new directory, change its name to junit-frames.xsl and use the task's styledir attribute to point to it. You will also need a compatible (older) version of Xerces. as well as BSF(bsf.jar). Again, using Xalan 2 is simpler and supported."
The javadoc prescribes to go the route of noframes, which kind of defeates the purpose of creating a decent test report
BTW i am using jdk1.3.1, if that makes any sense. [ August 23, 2004: Message edited by: Kishore Dandu ]
Joined: Jan 23, 2002
At least you have a problem where the <junit> task generates test results (TEST-*.xml) into the current directory but you're telling <junitreport> to look for them in a directory named reports.
Joined: Jul 10, 2001
thanks for the correction.
It works nice and generates a no frames html(when report format selection is noframes).
But if I have report format changed to frames, the output is not very user friendly. Any ideas??
I get the following exception during the frames report generation.