Scenario Outline: eating Given there are <start> cucumbers When I eat <eat> cucumbers Then I should have <left> cucumbers Examples: | start | eat | left | | 12 | 5 | 7 | | 20 | 5 | 15 |
Can I externalize the examples? Examples: file.table
Like the jBehave implementation - http://jbehave.org/reference/stable/parametrised-scenarios.html (scroll to
Or - does anyone know of a similar solution of parametrization?
Thanks,
Bogdan
--
Thanks,Bogdan
Posting rules: http://cukes.info/posting-rules.html
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Plain text is like living document. And if your document is too ugly with a lots of column in the feature file. It is not nice view for PO or BA. They don't care about dataset.
The Cucumber features you propose would add technical details into
feature files, that is exactly the opposite of what Cucumber is about.
Why should stakeholders know that there is a file to be read that has
some data that is needed by the glue code? If you need that, your
features are probably not readable by the stakeholders without
previous knowledge (e.g. knowing what should be in those files), and
you are likely using Cucumber as a test automation tool.