4 ms·

I'd agree with that. The education around proper utility of cucumber is definitely a problem.

• astrodust 13y ago
  Proper utility: Do not use. I've seen people try and fail to use Cucumber effectively. Now, Cucumber is a really impressive implementation, but it's a fundamentally flawed idea. You cannot pivot your requirements from business talk "As a blah I want X" into functional tests without a lot of shear. You may as well write your test descriptions in Farsi or Russian for a team that only speaks English. They make no sense. Functional requirements should set the groundwork, but they shouldn't serve as the template for construction. You convert these requirements into a format and language understood by developers. If you can preserve some kind of mapping between the original requirement and the myriad of things that had to be implemented to make that feature work, you've done something amazing. Sadly, Cucumber doesn't let you do that.
  • karmajunkie 13y ago
    Your premise is fundamentally flawed if you're using "functional tests" as a technical term (cucumber is not a functional testing tool) and just wrong if you're using it as a descriptor. Just because you've seen people try and fail to use cucumber effectively doesn't mean it can't be done. I would go so far as to say if you can't do it, you should reexamine how both how you're writing your tests, and how you're writing your application.