Hacker News Reader

Comment by mattvanhorn | Hacker News Reader

I've posted a response here: http://mattvanhorn.com/2013/09/19/a-case-for-cucumber/

Your case, while very valid, doesn't address the original author's concerns related to implementing the tests. In that case I feel as if it's equivalent to using GOTO in my tests. But worse, my labels are regex.

We use cucumber extensively, our cucumber suite is not really that large, and with each new feature it becomes harder to maintain. There has to be some middle ground out there.

I don't find implementing the tests very difficult at all - but I am comfortable with regular expressions, and ruby.

It's no more burden to write step definitions than it is to write RSpec directly. I use SOLID OOP to write my tests, most of the logic lives in regular old methods, and my steps look like:

  Then 'the current subscription payment date should be tomorrow' do
    verify_next_payment_date(Date.today + 1)
  end

Since I start with the Gherkin file, I type less than 10 keystrokes to make the step.

Reply on news.ycombinator.com