[LRUG] Writing readable feature tests with RSpec

[James Turley]

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.

I guess if you did want to optimise for code reuse, you could abstract
common factory/setup methods into a module and include that?


On Fri, Jul 25, 2014 at 10:26 AM, Joel Chippindale <
joel.chippindale at futurelearn.com> wrote:

> We recently blogged about how, at FutureLearn, we write readable feature
> tests with RSpec*, see
> https://about.futurelearn.com/blog/how-we-write-readable-feature-tests-with-rspec/,
> and it made me wonder how common this approach was.
>
> Are any of you using this approach already? If so, how are you finding it?
>
> J.
>
>
> * Hat tip to the developers at Econsultancy who introduced me to this way
> of using RSpec.
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> Archives: http://lists.lrug.org/pipermail/chat-lrug.org
> Manage your subscription: http://lists.lrug.org/options.cgi/chat-lrug.org
> List info: http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20140725/93a22fbe/attachment-0003.html>