From: Jeff Garland (jeff_at_[hidden])
Date: 2002-07-23 11:17:52
> >Any chance you could post the XML the report was based on?
>
> There is one file per test/toolset. For an example, see below. I added
> some newlines to make it easier to read.
I wonder then if it would be of benefit to generate one .html file for each .xml file instead of combining them? I noticed when I
hit one of the 'Fail' links and then returned to summary page that all of the 'Fail' links where colored as if I had visited each
one. It would be nice if only the one I actually navigated to was highlighted. Since web browsers only track visits on the file
level this would require one html file per toolset per test.
I also agree with Dave that an overall summary page by library would be a really nice. The page is already long and as boost
grows and adds more tests this is going to get out of hand. I'm thinking something like:
Summary Results for 2002-07-23 15:24:00 for Win32 -- 3 toolsets:
* GCC 3.1
* Borland
* Metroworks
library #tests failures warn missing
filesystem 3 0 1 0
thread 1 0 1 0
tokenizer 5 2 0 0
Library names would then hyperlink to an html file which contains only the results for that library.
Finally, from the library author perspective is there a reference for what we need to do to get our tests plugged into the system?
Great work!
Jeff