Open lseongjoo opened 8 years ago
Changing tag value to v0.31.0 to match the electron version will do the job. Still, it might be better to check bootstrap arguments accordingly.
Unless you need to run custom versions of Electron, you don't need to use this Grunt task, you should definitely use electron-prebuilt
instead
I need to use selenium webdriver for testing. Webdriver requires app's binary path so I am packaging it. Is there better way? If there is, I want to be informed. Thank you.
Unless you need to run custom versions of Electron, you don't need to use this Grunt task, you should definitely use electron-prebuilt instead
— Reply to this email directly or view it on GitHub https://github.com/paulcbetts/grunt-build-atom-shell/issues/37#issuecomment-134279842 .
Yes. When 3. Connect to chrome driver,
it seems that {chromeOptions: {binary: MyApp.app/Contents/MacOS/Atom}} requires the app's binary.
And I understand that the Workflow states that testing application w/o rebuilding is possible, but eventually I need to package my app. So I figure that Rebranding by rebuilding Elector from source applies. It says changing name from 'electron' is tedious so using grunt is better.
However, I've found this electron-packager http://git.io/vsyDN
I am reviewing this is the tool that I need. Can this be a way of doing things?
- 25., 오전 11:43, Paul Betts notifications@github.com 작성:
Have you seen https://github.com/atom/electron/blob/master/docs/tutorial/using-selenium-and-webdriver.md?
— Reply to this email directly or view it on GitHub.
You should definitely use electron-packager
Thank you, Paul.
- 25., 오후 12:19, Paul Betts notifications@github.com 작성:
You should definitely use electron-packager
— Reply to this email directly or view it on GitHub.
System is as below:
node v0.12.2 electron v0.31.0
Gruntfile.js as below: