1. 11
  1.  

  2. 4

    This is one of the few times I’ve been excited about the use of Cucumber.

    Too often, the readability of Cucumber is wasted, because the only people reading the Cucumber are the application developers, who are already fluent in the language of choice for that application, and would be just as comfortable reading tests written in that native language.

    I’m skeptical of the claim that Cucumber can be used to communicate directly to “non-technical stakeholders” with much success.

    However, for tests specifically designed as a stand-alone project to test a public api, this value could actually be realized. As an Android programmer, I don’t want to be reading / writing a lot of JavaScript / Ruby in order to propose an update to our API. But I do generally have input into API changes. Cucumber could serve as a bridge between programmers of different languages very nicely.