This project is read-only.

Report formatting for class-per-scenario

Feb 17, 2011 at 1:28 AM


I use class-per-scenario because I like the way that the class naturally provides a scope for the scenarios context - but the resulting html output is not the best. Each scenario is listed separately with a new copy of the story. Looking at the xml output I can see why. It is organised by code hierarchy (namespace, class, method) not by the logical hierarchy (story, scenario). 

Is there a way to get the scenarios grouped by story, instead of by class or do I need to write my own xslt?



Mar 1, 2011 at 10:29 PM

Sorry for the slow reply.


There's nothing built in, but I would love it if we could group our scenarios by story. Maybe the hierarchy would be dll > namespace > class > story > scenario. That way it wouldn't really matter what you called your test methods (would that be a good thing?)

This might involve rewriting the XML generator to do some fancy grouping, since you could end up with different instances of a story even though it has the same text.