<div dir="ltr">It's an interesting approach. I too have been suspicious of cucumber in terms of adding an extra dependency and an extra stage to the testing process. Readability for non-technical people is not a problem I've faced directly, though. <div>
<br></div><div>I guess if you did want to optimise for code reuse, you could abstract common factory/setup methods into a module and include that?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 10:26 AM, Joel Chippindale <span dir="ltr"><<a href="mailto:joel.chippindale@futurelearn.com" target="_blank">joel.chippindale@futurelearn.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">We recently blogged about how, at FutureLearn, we write readable feature tests with RSpec*, see <a href="https://about.futurelearn.com/blog/how-we-write-readable-feature-tests-with-rspec/" target="_blank">https://about.futurelearn.com/blog/how-we-write-readable-feature-tests-with-rspec/</a>, and it made me wonder how common this approach was.<div>

<br></div><div>Are any of you using this approach already? If so, how are you finding it?</div><div><br></div><div>J.<br><div><br></div><div><br></div><div>* Hat tip to the developers at Econsultancy who introduced me to this way of using RSpec.</div>

</div></div>
<br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote></div><br></div>