Eliminate Format as a factory for StoryReporter

Not following the line of thought. Format allows to easily define different formats and reporters.

What would replace it?

I would 'new up' reporters where I need them.

However I could be misunderstanding the nature of the linkage between the two. In a given a given run, for say "Console Output" how many times will createStoryReporter(..) be called? Once per story? or Once per run?

I assume it is the latter, as the console remains constant for the duration of the run. With the latter a single instance of ConsoleOutput spanning multiple stories (say in parallel) could detangle the output so that it makes sense in the shared output. Without that "whole run" view of the essential visitation of the methods, a whole run style of reporting will not be possible.

The main usecase for the Format is to abstract the interaction with the StoryReporterBuilder, which creates the FilePrintStreamFactory and hands it over to the Format.createStoryReporter() method. It also makes it much simpler to define reporters in the configuration.

The StoryReporterBuilder.build(path) method is invoked once per story (via the Configuration.storyReporter(path)) in the StoryRunner.

I'm struggling to see how the Format may feel an unncessary separation. IMO, Format.HTML or new Format("HTML") is simpler than

public static final Format HTML = new Format("HTML") {

        @Override
        public StoryReporter createStoryReporter(FilePrintStreamFactory factory,
                StoryReporterBuilder storyReporterBuilder) {
            factory.useConfiguration(storyReporterBuilder.fileConfiguration("html"));
            return new HtmlOutput(factory.createPrintStream(), storyReporterBuilder.keywords()).doReportFailureTrace(
                    storyReporterBuilder.reportFailureTrace()).doCompressFailureTrace(
                    storyReporterBuilder.compressFailureTrace());
        }
    };