I'm currently working on this integration and it will take a few iterations to get it right. In the meantime, I will continue posting updates of the xsl on here in case any one wants to offer feedback. I will leave a comment when I feel this issue is complete.
Do you plan to write an xsl to integrate in CC to provide dedicated formatting or do you want to stay on the webtest results -> junit results?
Initially I'll stay on webtest->junit track. That way users of other automated build systems (e.g. hudson) could use this as well. The junit format seems to be the only "standard" amongst the different ci servers.
Once that is done, I'll probably go ahead and write an xsl specific to cruisecontrol integration. We can probably contribute this to their project and hopefully get them to support some out of the box functionality for webtest.
I'm a firm believer that when things are supported with very little configuration, adoption will be become more prominent.
I agree that both make sense.
Concerning the second point, it is probably wise to develop it for the "new" format.
An update to get error messages in email.
attaching a screenshot of the email i know receive from cruisecontrol
Since build 1654, using webtest.xml a WebTestOverview.junit.xml file is automatically created in the results folder. The information provided is not as rich as in your proposition which doesn't apply to the new result format.
I close this issue. Improvements to the generation of WebTestOverview.junit.xml are welcome as new issues.