2

Closed

Separating Report Type configuration from specs.

description

I think creating reports should be separated from tests, so one ExecuteWithReport method would be enough. but at the same time report generation should be configurable somehow. Currently when I want to change e.g. from Simple report to regular report, I have to go through all me specs and change the method directly in them, which is not a good thing to do.
Closed Apr 1, 2010 at 1:54 PM by robfe

comments

robfe wrote Mar 8, 2010 at 2:24 PM

Hi HEskandari.

Both toddb and I agree :)

I am curious, though, what you think about us merging the two reports into one? I am planning to build a new xslt that will transform the storyq.xml into a javascript-enabled html page, similar to the (non simple) report we currently have.

Are there any features of the simple report that make you want to use it instead of the rich one?

robfe wrote Mar 16, 2010 at 2:05 PM

I am going to have to leave the SimpleHtmlReport in, since it's the only one that works in IE6. In order to not have to change all the specs, i'll delete ExecuteWithSimpleReport, and make ExecuteWithReport check a value in the StoryQSettings static class (probably something like bool SupportLegacyBrowsers)

Sign in to add a comment