Ruby: Ways to prevent cucumber reduncancies? -
does have idea how make shorter , less redundant: feature: nosql scenario: flatfile user wants have flatfile storage classic jekyll cms. when case should make sure adhere classic folder , file structure, , store generated content in _site unless user decides want generation stored inside of memcached, should go ahead , use that. given have chosen flatfile storage site when request page, "the_page" , have chosen flatfile generation should pull page "_site" given have chosen flatfile storage site when request page, "the_page" , have chosen memcached generation should pull page memcached i see repeated text , though cucumber meant people communicate seems it's made things perhaps "too dumb" because of repetition in types of scenarios? unless missing something. there other small problem, how make 1 feature have dependency of feature? example memcached feature how require feat...