On Fri, Mar 17, 2006 at 01:06:32PM -0800, David Daney wrote: > Thomas Fitzsimmons wrote: > >Hi, > > > >Anthony Balkissoon has expressed interest in improving Mauve so we'd > >like to know what would be the best things to work on. > > > >Here are two items on my list: > > > >- A web reporting facility that generates JAPI-style bar graphs. > >Ideally the graphs would represent a code-coverage analysis but I have > >no idea how feasible that is using free tools. > > > >- A framework for testing VM invocations and the tools' command-line > >interfaces -- in other words, a framework that can exec commands. This > >may be best done as an independent module, separate from Mauve. > > > >There is also lots of room for improvement in how Mauve tests are > >selected and run. I'm hoping someone who better understands Mauve's > >design will elaborate. > > > > I would like to see a way to partition the different tests. Sometimes > mauve will not build for gcj (and probably other compilers as well) > because just a single file has some problem. It would be nice to still > be able to run the majority of the tests in this situation. That is what batch_run can do today. Cheers, Michael -- http://www.worldforge.org/
