This project is read-only.

Output format - HTML

Coordinator
Sep 6, 2008 at 5:13 PM
In order to easily survey the results
As a person reading the builder server results
I want to be able to change the view of results

Functions:
 - combo box for recategorising the tests (Namespace, Project Structure, Categories[?])
 - tree view of results [pane 1] - click to view below
 - results [pane 2]

We going to need some aggregates of tests for passed, failed, pending
Some icons for namespace '{}', project structure 'folders', categories, passed, failed, pending

Basic design

 - Leave default HTML and plain text writer in place
 - Add a new XML writer with manifest file

For the xml writer:

generate each xml file
 . individual result xml file

include a manifest file
  - imports each files based on the XPath include from filesystem
 - does xslt to html
 - puts in jQuery
 - displays as html

Retain separation in source code
 - js
 - js table sorter
 - css

Target Firefox!

Future
 - be able to configure up a new css skin via an optional XML file eg config.xml
Oct 20, 2009 at 11:53 AM

It's really embarrassing, but I didn't see this post before I went about rolling my own (simplified) solution (see my thread named "Story Status Web Report in TeamCity" above).

It's totally build server agnostic, despite the thread name, and doesn't use aggregation, but rather XML deserializes a List<StoryStatusItem> as it runs.

I'll be happy to send you my modified version of the trunk for inspiration.

Coordinator
Oct 21, 2009 at 7:36 AM

Please do! If you could flick a ZIP through to robert [dot] ensor [you know what] gmail [dot] com.

I've got plans to overhaul StoryQ using flit.codeplex.com, so now's a great time for inspirational code :)

Nov 13, 2009 at 8:08 AM

Did you receive the ZIP file I sent a few weeks ago?

Also, I'm playing around with more exception info when those occur, since it's really helpful to get the stack trace, etc.