{"push_id":879852634,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"e9b99644bbc40ab4f97dafb81bca46dbbc0054b0","before":"b6c394432a88fee1b06ac26f17a021db44c6f785","commits":[{"sha":"e9b99644bbc40ab4f97dafb81bca46dbbc0054b0","author":{"email":"d2de768c75921b592d5c23701d3bf9aa21f06d11@gmail.com","name":"Darrin Holst"},"message":"Use Cucumber.Cli to run features\n\nThis changes the way we run cucumber to be the same way you would\nrun it from the command line. This way we get the same default\noptions that you normally would, i.e. color (see\nhttps://github.com/cucumber/cucumber-js/pull/457#issuecomment-157792257).\nIt should be more stable as well and not break with internal\ncucumber changes.\n\nAlso, instead of hacking into one of the formatters to get the\nresults it uses cucumber's events to do it now.\n\n`cucumberOpts` now have a 1-to-1 mapping to cucumber cli arguments.\nFor example the following options...\n\n```javascript\n  cucumberOpts: {\n    format: ['json:./build/test-results/protractor.json', 'pretty'],\n    require: ['features/step_definitions/**/*.js', 'features/support/**/*.js'],\n    'no-source': true,\n    strict: true\n  },\n```\n\nwould be converted to the following cucumber command...\n\n```\n  cucumberjs \\\n  --format json:./build/test-results/protractor.json \\\n  --format pretty \\\n  --require features/step_definitions/foo.js \\\n  --require features/step_definitions/bar.js \\\n  --no-source \\\n  --strict \\\n  foo.feature \\\n  bar.feature\n```\n\nThis way there _shouldn't_ be any changes needed in this library to\nsupport new cucumber options.","distinct":true,"url":"https://api.github.com/repos/darrinholst/protractor-cucumber-framework/commits/e9b99644bbc40ab4f97dafb81bca46dbbc0054b0"}]}