chore(scripts): avoid duplicate work and update docs

Author: gkalpak

scripts/private/README.md

@@ -18,21 +18,15 @@ repository. The folder structure of this branch is different to the main master
 copied to its own folder.
 
 - **update-gh-pages.sh**: Run this script to copy changes to the tutorial steps and bower 
-  dependencies over to the gh-pages branch.
-
-Once you have updated the local gh-pages branch you can review the changes and push to the remote
-gh-pages branch on GitHub.
-
-```
-git push origin gh-pages
-```
+  dependencies over to the gh-pages branch and (if all tests pass) push to the remote gh-pages
+  branch on GitHub.
 
 ### Auto-updating Demo Pages from CI
 
 There is a Jenkins job that runs periodically and executes `jenkins.sh`.
 
 - **jenkins.sh**: This script will set the Node.js version to 4.x (using `nvm`), will run all the
-  tests (using `test-all.sh`) and update the demo pages (using `update-gh-pages.sh`).
+  the tests and update the demo pages (using `update-gh-pages.sh`).
   (You shouldn't need to run this script manually.)
 
 ## Pushing to GitHub

scripts/private/jenkins.sh

@@ -6,8 +6,5 @@ source ~/.nvm/nvm.sh
 # Use Node.js v4.x
 nvm install 4
 
-# Run all tests
-scripts/private/test-all.sh
-
-# Publish steps on gh-pages
+# Run all tests and publish steps on gh-pages
 scripts/private/update-gh-pages.sh

scripts/private/test-all.sh

@@ -18,7 +18,7 @@ BRANCH=$(git rev-parse --abbrev-ref HEAD)
 npm install
 
 # Ensure that the chromeDriver is installed
-npm run update-webdriver
+node_modules/.bin/webdriver-manager update --gecko false --standalone false
 
 # Start up the web server
 node_modules/.bin/http-server ./app -a localhost -p 8000 -c-1 --silent &

scripts/private/update-gh-pages.sh

@@ -6,12 +6,12 @@
 #
 # The tutorial step changes are computed by checking out each step into a snapshot folder and then
 # overwriting the step folders in gh-pages with these new ones.
-# If there are any changes they will be committed
+# If there are any changes they will be committed.
 #
 # The dependency changes are computed by running "bower update" then committing any changed files
 # inside the bower_components folder onto the gh-pages branch.
 #
-# You should review these commits and push them to origin/gh-pages if valid.
+# Finally, the new commits are pushed to origin/gh-pages.
 
 # Exit on error and print each command as it is run
 set -ex