Add support for scenario outlines and examples.
It doesn't seem so critical after all. Should we delay this feature until there are people asking for it?
ahh, yes, it is SO CRITICAL. please spent some effort to it, it would be lovely.
btw. thanks for your presentation on BDD Node.js in London, it was excellent.
@vecernik thank you for the kind words.
@vecernik @vslinko Have a look at the discussion here: #75
Just adding my voice to the "cannot use cucumber-js until scenario outlines are supported" camp, small though it may be.
Sorry, After reading comments on #75, I changed my opinion and think it is not as useful as I thought.
I have to drop cucumber-js because of this. It's too bad, I was looking forward to writing everything in JS. This is a standard gherkin syntax format, and a DRY-er format that QA's seem to like looking at more than the standard.
Update: I'm working on it as we speak. I had it working on a branch but I was not happy with the implementation I came up with. I'm now rewriting it again with a better and more robust design. I hope I'll be able to release it within the next 10 days.
Let me know if I can do anything to assist: pgrenierATgmail.com
@jbpros How is the work going? I was just considering working on it myself, as I really need this feature.
@jbpros do you have an example of implementation somewhere?
I interested in seeing the right way to implement Scenario Outlines, describe the table with Examples, and then especially how to access those variables in the step definition methods (given/when/then).
Scenario outlines are just a way to shorten the amount of gherkin you write and don't have an effect on running. The scenario outline gets expanded into scenarios with the variables replaced.