<div dir="ltr">> <span style="font-family:arial,sans-serif;font-size:13px">I have never been sold on cucumber, it just seems like testing mastrubation.</span><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Bwahaha! To each his/her own I suppose, (there's plenty in my toolchain that others would find totally worthless) but I've been told that masturbation is definitely more fun than Cucumber.<br>
</font><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">/switches on Tom Stuart bat signal</span><br></div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 11:32 AM, James McCarthy <span dir="ltr"><<a href="mailto:james@lety.co" target="_blank">james@lety.co</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    I have never been sold on cucumber, it just seems like testing
    mastrubation.<br>
    <br>
    Unit testing and some integration testing yes but much more than
    that is it becomes and end to itself, testing for the sake of
    writing tests.<br>
    <br>
    James.<div><div class="h5"><br>
    <div>On 25/07/14 11:16, James Turley wrote:<br>
    </div>
    <blockquote type="cite">
      <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" target="_blank">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>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Chat mailing list
<a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a>
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>
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>
</pre>
    </blockquote>
    <br>
    </div></div><pre cols="72">-- 
James McCarthy

Software Engineer

LetyCo - Analyse, Build, Deliver
Ruby/Rails software for London and the SouthEast.
 
Mob:  07577006897

Email:  <a href="mailto:james@lety.co" target="_blank">james@lety.co</a>

<a href="http://lety.co" target="_blank">lety.co</a></pre>
  </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>