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.

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

changing the run webdriver manager to run e2e tests #304

Closed
wants to merge 1 commit into from
Closed

changing the run webdriver manager to run e2e tests #304

wants to merge 1 commit into from

Conversation

MarcosSpessatto
Copy link

Removed webdriver-manager from postinstall, and added to the "test:e2e" instruction. Changing, because "npm install --prod" not working, and broke installation for the production enviroment only.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 99.18% when pulling 7857c9b on MarcosSpessatto:master into e2fabe9 on assisrafael:master.

@@ -14,13 +14,12 @@
"lint": "eslint *.js src/ config/ --fix",
"test": "npm run test:unit && npm run test:e2e",
"pretest:e2e": "npm run build",
"test:e2e": "protractor config/protractor.conf.js",
"test:e2e": "npm run webdriver && protractor config/protractor.conf.js",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of calling the webdriver task here you should have used the ci task. Because running the webdriver task every time you run the e2e task will make development really slow.

@assisrafael
Copy link
Owner

Thank you for the pull request.
Please check the comment in the diff.
And let me know when you fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants