Cucumber tests for cucumber-js include a number of undefined steps

[simondean]

Hi. cucumber-js uses Ruby Cucumber and cucumber-js to test itself. The output from these two test runs include a number of undefined scenarios. It's not possible to know if these undefined scenarios are masking regressions. It would be good to use the --strict option with Ruby cucumber and cucumber-js when cucumber-js tests itself.

Ruby Cucumber is executed from the Rakefile

  desc "Run the features through Cucumber (Ruby) and Aruba"
  task :rb do
    sh %{ cucumber -p quiet }
  end

cucumber-js is executed from the package.json

  "scripts": {
    "test": "./bin/cucumber.js && jasmine-node spec"
  },

[simondean]

This issue would make use of #58

[jbpros]

I had a discussion with @samccone about this. We'd like to only keep the JS suite in the long term, that would probably lower the barrier for entry for people willing to contribute.

[jbpros]

#58 is done. We can do this now!

[charlierudolph]

Fixed in 8daf95b

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.