1. NPM Module and Bower component support.

Updated package.json and gulpfile to allow publishing a NPM module.

Added a bower.json file to publish a Bower component.

Creating a NPM module basically consisted of adding some information in the package.json
(`main` - main JS file of the module - and `style` - main stylesheet - properties) and
precompiling everything into the dist/ folder. This way developers will have access
to the compiled code when installing the module in their project (`npm install
firebaseui`). The default gulp command will automatically generate the NPM module.

Bower packaging consists of creating the bower.json file. It contains metadata on the
component. Developers can then run `bower install firebaseui` and fetch the JS and CSS
files in their app by using paths to the dist folder of the bower components
(e.g. src="bower_components/dist/firebase-ui-auth.js")

Bower file specs:
https://github.com/bower/spec/blob/master/json.md

2. Travis and SauceLabs support.
Configured Travis to run tests on SauceLabs.

I've added a new command:
npm test
that alias npm run test. It is also the usual default command to run tests in a
NPM project.
See the sauce_browsers.json file for the list of browsers covered.

It sill supports running phantomJS by default, so developers can use it in their local
env.

How it works:
SauceConnect creates a tunnel to remote instances of SauceLabs browsers, which exposes
the localhost to the remote instance. This tunnel gets attributed an ID. Protractor
then uses this ID to connect to the distant browser and run tests. The HTTP server
that serves test files is run locally, and the tunnel is meant for the remote instances to
access it.
When using Travis, SauceConnect will be automatically started by the process (it's an
addon directly offered by Travis). The tunnel ID will be exposed as the
TRAVIS_JOB_NUMBER.

Travis configuration:
https://docs.travis-ci.com/user/languages/javascript-with-nodejs/
Notice I'm using the secure way of storing the access key, so it can safely be pushed
to the public GitHub repo.

SauceLabs configuration for Travis:
https://docs.travis-ci.com/user/sauce-connect/

Using protractor with SauceLabs:
https://support.saucelabs.com/customer/portal/articles/2029412-running-protractor-tests-on-sauce-labs
A lot of things happen under the hood here, like connecting to the remote browser
Webdriver instance through the tunnel.

PiperOrigin-RevId: 139406176
Change-Id: Ie5ca57218b3df5ccaee3fc187b8ac20ac31618fd

Author: Googler

.travis.yml

@@ -0,0 +1,12 @@
+language: node_js
+node_js:
+  - '6'
+  - '6.0'
+  - '6.1'
+install: npm install
+script: npm test -- --saucelabs
+addons:
+  sauce_connect:
+    username: firebaseui
+  jwt:
+    secure: N2XxNudp1yIYrXZ1LIQVnVWW4L5doPIws6a10SHzxttigRXNDK2gQycVTN1MVwyVElVjPyyrLdsB9eRp0fSa0O6/MLc6tlbmt4cOT/zIi96ii3G6L5no9Yod8W5LAr4l2paB9apInghC2zetPGxCS4sW9vKEsIwzTIZZTBnq9AVfU0kpScgnD8/etiYljVTzXp36B65a2T9rXPXnhXKwYyX+TBRULJWhmHoM3FJwUxhMoa41XxxD1+0Zhd+lvBLzPjkRoUUJLR+JFpBDvjhtRkARPiAG+3r07ycrYZAMB87ZypBJOJBrUYA4KlxotPZc7jYEeAmiWJxDoZwwJQeyoI9J42fMEcdqzn7a6bm59jpKHXRwPNed2EY19BtBpXcYMjJRxLFSgWbrKw/hcqi9waaFBO/SXaCtUGPamxYSBHUaS1ljAR7omDkq2aeQAV2E4lgD9od3sgXGqCWzdl33erm4cWgjaNGVQlpNzBdG8zm3C870+x5+pvlsM2/lPCA0RIkIcA5uPmBmQlB8cgzfBCh0x5r6C9wl3TWGW9LaJAB9WZpgkmGk92A1sCnVRufaNYNJm8CwTxM2IK/3xWRc0bEdXpY3I4vA0uMelitWDI9wBIT+HN9TWPQUHzStjlP8PwBAZxf4ab2bB+GLEa5yUyiERK3iyHmX8gvFo14fPEw=

README.md

@@ -447,7 +447,7 @@ how to configure the app to be deployed on a Firebase Hosting instance.
 All unit tests can be run on the command line (via PhantomJS) with:
 
 ```bash
-npm run test
+npm test
 ```
 
 Alternatively, the unit tests can be run manually by running

bower.json

@@ -0,0 +1,27 @@
+{
+  "name": "firebaseui-web",
+  "version": "1.0.0",
+  "description": "Javascript library for customizable UI on top of Firebase SDK",
+  "main": [
+    "./dist/firebase-ui-auth.js",
+    "./dist/firebase-ui-auth.css"
+  ],
+  "authors": [
+    "Google"
+  ],
+  "license": "Apache-2.0",
+  "keywords": [
+    "Firebase",
+    "authentication"
+  ],
+  "homepage": "https://github.com/firebase/firebaseui-web",
+  "ignore": [
+    "**/.*",
+    "node_modules",
+    "generated",
+    "out"
+  ],
+  "dependencies": {
+    "firebase": "^3.3.0"
+  }
+}

buildtools/run_tests.sh

@@ -17,30 +17,72 @@
 # creates a local webserver to serve test files, and run protractor.
 #
 # Usage:
-# $ buildtools/run_protractor.sh
+#
+# ./buildtools/run_tests.sh [--saucelabs [--tunnelIdentifier=<tunnelId>]]
+#
+# Can take up to two arguments:
+# --saucelabs: Use SauceLabs instead of phantomJS.
+# --tunnelIdentifier=<tunnelId>: when using SauceLabs, specify the tunnel
+#     identifier. Otherwise, uses the environment variable TRAVIS_JOB_NUMBER.
+#
+# Prefer to use the `npm test` command as explained below.
+#
+# Run locally with PhantomJS:
+# $ npm test
+# It will start a local Selenium Webdriver server as well as the HTTP server
+# that serves test files.
+#
+# Run locally using SauceLabs:
+# Go to your SauceLab account, under "My Account", and copy paste the
+# access key. Now export the following variables:
+# $ export SAUCE_USERNAME=<your username>
+# $ export SAUCE_ACCESS_KEY=<the copy pasted access key>
+# Then, start SauceConnect:
+# $ ./buildtools/sauce_connect.sh
+# Take note of the "Tunnel Identifier" value logged in the terminal.
+# Run the tests:
+# $ npm run -- --saucelabs --tunnelIdentifier=<the tunnel identifier>
+# This will start the HTTP Server locally, and connect through SauceConnect
+# to SauceLabs remote browsers instances.
+#
+# Travis will run `npm test -- --saucelabs`.
 
 cd "$(dirname $(dirname "$0"))"
 
-./node_modules/.bin/webdriver-manager update
-
 function killServer () {
-  # Selenium Webdriver starts one child process from this one.
-  # This command kills them all.
-  kill -- -$seleniumPid
+  if [ "$seleniumStarted" = true ]; then
+    echo "Stopping Selenium..."
+    ./node_modules/.bin/webdriver-manager shutdown
+    ./node_modules/.bin/webdriver-manager clean
+  fi
+  echo "Killing HTTP Server..."
   kill $serverPid
 }
 
-# Start Selenium Webdriver.
-./node_modules/.bin/webdriver-manager start &>/dev/null &
-seleniumPid=$!
-
 # Start the local webserver.
 ./node_modules/.bin/gulp serve &
 serverPid=$!
+echo "Local HTTP Server started with PID $serverPid."
 
 trap killServer EXIT
 
-# Wait for servers to come up.
-sleep 10
-
-./node_modules/.bin/protractor protractor.conf.js
+# If --saucelabs option is passed, forward it to the protractor command adding
+# the second argument that is required for local SauceLabs test run.
+if [[ $1 = "--saucelabs" ]]; then
+  seleniumStarted=false
+  sleep 2
+  echo "Using SauceLabs."
+  # $2 contains the tunnelIdentifier argument if specified, otherwise is empty.
+  ./node_modules/.bin/protractor protractor.conf.js --saucelabs $2
+else
+  echo "Using PhantomJS."
+  # Updates Selenium Webdriver.
+  ./node_modules/.bin/webdriver-manager update
+  # Start Selenium Webdriver.
+  ./node_modules/.bin/webdriver-manager start &>/dev/null &
+  seleniumStarted=true
+  echo "Selenium Server started."
+  # Wait for servers to come up.
+  sleep 10
+  ./node_modules/.bin/protractor protractor.conf.js
+fi

buildtools/sauce_connect.sh

@@ -0,0 +1,57 @@
+#!/bin/bash
+# Copyright 2016 Google Inc. All Rights Reserved.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS-IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+#
+# Download and install SauceConnect under Linux 64-bit. To be used when testing
+# with SauceLabs locally. See the instructions in protractor.conf.js file.
+#
+# It should not be used on Travis. Travis already handles SauceConnect.
+#
+# Script copied from the Closure Library repository:
+# https://github.com/google/closure-library/blob/master/scripts/ci/sauce_connect.sh
+#
+
+# Setup and start Sauce Connect locally.
+CONNECT_URL="https://saucelabs.com/downloads/sc-4.4.1-linux.tar.gz"
+CONNECT_DIR="/tmp/sauce-connect-$RANDOM"
+CONNECT_DOWNLOAD="sc-latest-linux.tar.gz"
+
+BROWSER_PROVIDER_READY_FILE="/tmp/sauce-connect-ready"
+
+# Get Connect and start it.
+mkdir -p $CONNECT_DIR
+cd $CONNECT_DIR
+curl $CONNECT_URL -o $CONNECT_DOWNLOAD 2> /dev/null 1> /dev/null
+mkdir sauce-connect
+tar --extract --file=$CONNECT_DOWNLOAD --strip-components=1 \
+    --directory=sauce-connect > /dev/null
+rm $CONNECT_DOWNLOAD
+
+function removeFiles() {
+  echo "Removing SauceConnect files..."
+  rm -rf $CONNECT_DIR
+}
+
+trap removeFiles EXIT
+
+# This will be used by Protractor to connect to SauceConnect.
+TUNNEL_IDENTIFIER="tunnelId-$RANDOM"
+echo "Tunnel Identifier: $TUNNEL_IDENTIFIER"
+
+echo "Starting Sauce Connect..."
+
+# Start SauceConnect.
+sauce-connect/bin/sc -u $SAUCE_USERNAME -k $SAUCE_ACCESS_KEY \
+    -i $TUNNEL_IDENTIFIER