There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
support Test per Scenario in StoryQ GUI Converter
Just a personal preference here, but my preferred test style the test method-per-scenario approach, with a single story per test fixture/class (exactly as demonstrated in the StoryQ.Converter.Wpf.Specifications project in the source code, right down to
the use of the SpecificationBase base class).
Each test fixture/class is named after the story, and each test method is named after the scenario.
It would be a great time saver if this style could be added to the supported code generation strategies in the GUI converter.