Optimize for production with Vulcanize -- Polycasts #39

Subscribers:
791,000
Published on ● Video Link: https://www.youtube.com/watch?v=EUZWE8EZ0IU



Duration: 7:49
14,541 views
312


It's important to get a good testing setup in place for your project as early as possible. Using services like Travis for continuous integration, and Sauce Labs for cross-browser testing means you can be confident that changes you push to your project will work well on different platforms and devices. But setting these tools up can be pretty tricky! To help clear away some of the confusion I'll walk you through everything you need to get your first project up and running on both services.

Example Project (chart-elements)
https://github.com/robdodson/chart-elements

Travis CI
travis-ci.org

Sauce Labs
https://saucelabs.com/

Open Sauce
https://saucelabs.com/opensauce/

Sauce Labs Wiki
https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options#TestConfigurationOptions-RequiredSeleniumTestConfigurationSettings

Web Component Tester Plugins README
https://github.com/Polymer/web-component-tester#plugins

Polymer Tools - Travis
https://github.com/Polymer/tools/tree/master/travis

Travis Ruby Gem
https://rubygems.org/gems/travis/versions/1.8.0







Tags:
Chrome
Developers
Google
Web
Vulcanize
Polymer
Travis
Sauce Labs
Travis CI
web components
product: web
fullname: Rob Dodson
Location: MTV
Team: Scalable Advocacy
Type: Screencast
GDS: Full Production
Other: NoGreenScreen yt:cc=on