Configure OkCandidate Platform for Cucumber

[rydente]

Introduce Cucumber as an acceptance testing and feature collaboration
system to OkCandidate so we can define and verify the system from a
functional perspective based on the users' perspectives.

Signed-off-by: Ryan Y ryayak1460@protingumas.com

[wbprice]

What are the specific challenges with using the JavaScript implementation of Cucumber?

[rydente]

@wbprice From reading the recent documentation and checking up on collaborating toolsets, the teams involved may have mitigated them, but last I used it (November of last year):

• every step had to return a Promise;
• the headless browser (Zombie.js) hadn't had an update in a long time;
• Zombie didn't work properly in certain cases (cookies and ignoring self-signed certificates came to mind);

As a result, it read poorly (generally, features, scenarios and steps should read very, very clearly) and had lots of little bugs which made implementing steps take far longer than normal, made them flakier and harder to debug when they went wrong.

However, I'm still in the process of writing up a bdd-js PR that I will send out soon, at latest tomorrow, so would you want to wait for that to come in and make a decision then?

EDIT: It doesn't seem as bad as it used to. I'll put up two gists to compare how tests look and link to each.

Here's the Ruby gist. The related PR below gives the Cucumber.js example.

[wbprice]

We don't need this here if we have a LICENSE file in the project root.

[wbprice]

Closing this because we're probably going to use the JS implementation of Cucumber.