[Cucumber] Dealing with multiple, more complex set of scenarios per feature (in Feature File)
2014-04-16 10:09:27 GMT
We’ve started looking at Cucumber, and so far used it in our simpler user stories (features).
We’re keen to continue using this on features having multiple, more complex scenarios – on system-level, with more data variation.
And although there are several ways to deal with this programmatically in StepDefs (e.g. scenario outline, multi-line strings, data tables, etc), would appreciate some advice on dealing with more complex scenarios.
How should these be designed or implemented in a Feature File?
Would it make sense to have several Feature Files per feature? Splitting
closely-related scenarios in groups, with each group contained in a Feature
File? (though this means fragmenting the behaviors of the feature, which could
have potential disadvantages)
Please advice, thank you!
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+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit https://groups.google.com/d/optout.