-
Notifications
You must be signed in to change notification settings - Fork 724
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
Feature Request: Support Chrome Packaged Apps #2213
Comments
We don't have any knowledge about Chrome Packaged Apps unfortunately. What would be involved in testing these, in particular regarding the API privileges you've mentioned? |
Well, I'm not well versed in how Travis works, but you can signal Chrome to launch a Chrome App from the command line. I then typically bundle a jasmine test suite with my app and report back to a custom CI. Depending on what level of communication you require with the app, we can discuss options, but you can use web inspector on them etc. My point about API privileges was because Chrome Packaged apps can access to system API's like sockets, bluetooth, usb, etc. See more here: permissions. |
Have you had any luck setting up an app on Travis CI? |
I haven't tried, I assumed it would not be possible, and was just filing the issue on behalf of the Stack Overflow question. Does Travis allow specifying arbitrary shell commands for launching tests? I assumed you only launch pages by url, which won't work for a packaged app. |
You can run anything to run your tests. Just specify a custom |
I'm closing this for now. Let us know if you have any more feedback or questions on this. |
It's possible to run chrome headless and load packaged apps from command line flag. The real difficulty would be in setting up a sandboxed environment for them to run in, given the api privilages.
This was requested on Stack Overflow: http://stackoverflow.com/questions/23324523/with-travis-ci-how-do-i-test-chrome-packaged-apps
Will this ever be considered?
The text was updated successfully, but these errors were encountered: