Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Breasks with cucumber@4 #110

Open
dignifiedquire opened this issue Mar 15, 2018 · 1 comment
Open

Breasks with cucumber@4 #110

dignifiedquire opened this issue Mar 15, 2018 · 1 comment

Comments

@dignifiedquire
Copy link

The binary path has changed on unix to cucumber-js resulting in

Running "cucumberjs:ci" (cucumberjs) task
>> cucumberjs binary not found at path node_modules/cucumber/bin/cucumber.js
>>  NOTE: You cannot install grunt-cucumberjs without bin links on windows
@afonsobarrenha
Copy link

Same problem here,

{
"name": "cucumberjs-demo",
"version": "0.0.0",
"private": true,
"scripts": {
"clean": "rm -rf tmp"
},
"dependencies": {
"chai": "^4.2.0",
"chromedriver": "^75.1.0",
"cucumber": "^5.1.0",
"geckodriver": "^1.16.2",
"grunt": "^1.0.4",
"grunt-cucumberjs": "^2.0.2",
"selenium-webdriver": "^3.6.0"
}
}

devoto13 added a commit to devoto13/karma that referenced this issue Apr 19, 2020
@devoto13
build: run cucumber tests using NPM scripts instead of Grunt
7f2e8a9 
The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
devoto13 added a commit to devoto13/karma that referenced this issue Apr 19, 2020
@devoto13
chore(build): run cucumber tests using NPM scripts instead of Grunt
ccf9389 
The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
@devoto13 devoto13 mentioned this issue Apr 19, 2020
Merged
devoto13 added a commit to devoto13/karma that referenced this issue Apr 20, 2020
@devoto13
chore(build): run cucumber tests using NPM scripts instead of Grunt
99bd930 
The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
devoto13 added a commit to devoto13/karma that referenced this issue Apr 20, 2020
@devoto13
chore(build): run cucumber tests using NPM scripts instead of Grunt
c7fcc06 
The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
johnjbarton pushed a commit to karma-runner/karma that referenced this issue Apr 20, 2020
@devoto13
chore(build): run cucumber tests using NPM scripts instead of Grunt (#…
652e24e 
…3476)

The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
anthony-redFox pushed a commit to anthony-redFox/karma that referenced this issue May 16, 2023
@devoto13 @anthony-redFox
chore(build): run cucumber tests using NPM scripts instead of Grunt (k…
fe44f84 
…arma-runner#3476)

The main reason for this change is to be able to update Cucumber library as `grunt-cucumberjs` (mavdi/grunt-cucumberjs#110) does not support cucumber@4 and looks pretty abandoned.

Grunt ecosystem is not very active for a while, so we can expect more issues of this sort in the future. Because of this and to keep docs consistent I've also added NPM scripts to run other test types (for now they just proxy to Grunt) and removed Grunt examples from the documentation.

In the next PR I will update `cucumber` and perform some cleanup of the step definitions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dignifiedquire @afonsobarrenha