I made an addition to the latest trunk version in order meet my needs, i.e. produce an html report with the status of each story for a high level view of the system state.
- Each story assertion adds a StorySummaryItem to the report which is written in simple XML
- An XSLT file is added to the project which is copied to the output dir on build
- I've buit a simple MSBuild task that takes an XML, and an XSLT file as input, and outputs the result to a third file
- I run the XSLT task as a part of our continious integration process
The report looks like this for the StoryQ test suite (please note that the css is missing in this example, for example, it uses the same colors as the original story html reports of StoryQ):
StoryQ Story Set Summary
The hyperlinks links to the detailed html reports that StoryQ outputs when the story is asserted with the reporting option.
I'd be happy to supply my contribution in order for all StoryQ users to benefit from the high level story set summary report.