This project is read-only.

Data Driven stories / scenarios


Storyq needs a way to run the same story over different parameter datasets. Ideally, we'd aggregate the results (like in Caley's fork) and allow developers complete freedom regarding what the datasource is (passing an IEnumerable<T> would be good).


jlb0001 wrote May 16, 2011 at 9:40 PM

This issue and the initiating discussion thread ( reminds me of the "Examples" section that has been added to the "Scenario Outline" in Gherkin syntax. For the sake of additional conversation, here are some posts that show how that plays out in the Gherkin syntax. Since one of the goals for StoryQ is to covert from Gherkin, it's not terribly important that we use one style of parameter-driven tests vs another in the generated C# -- whatever works, since it'll be automatically generated most of the time, right?

"Examples" section in "Scenario Outline":

In reading about the ways that data tables have evolved in Cucumber / Gherkin, these are the best examples of the syntax I could find that relates to this issue:

This quickly gets tangled with another table concept used in Cucumber where the tables are treated as a parameter in and of themselves whereby the entire table is compared as a value (i.e., not used as a substitution data driven table source):

robfe wrote May 16, 2011 at 10:04 PM

Thanks jlb, I was just sitting down to work on this and these examples are very good inspiration.

jlb0001 wrote May 17, 2011 at 5:30 PM

Out of curiosity, does StoryQ use the official Gherkin parser? I noticed that SpecFlow updates this parser with each of their releases.

Gherkin Parser (official .NET implementation):

robfe wrote May 17, 2011 at 10:56 PM

No, the parser to convert text into StoryQ code is very rudimentary. The parser that creates the StoryQ fluent interface (a t4 template) is a bit different, it's based on Dot (