angular-cn/scripts/ci/test-aio.sh

#!/usr/bin/env bash

set -u -e -o pipefail

# Setup environment
readonly thisDir=$(cd $(dirname $0); pwd)
source ${thisDir}/_travis-fold.sh


# run in subshell to avoid polluting cwd
(
  cd ${PROJECT_ROOT}/aio


  # Lint the code
  travisFoldStart "test.aio.lint"
    yarn lint
  travisFoldEnd "test.aio.lint"


  # Run PWA-score tests
  # (Run before unit and e2e tests, which destroy the `dist/` directory.)
  travisFoldStart "test.aio.pwaScore"
    yarn test-pwa-score-localhost
  travisFoldEnd "test.aio.pwaScore"


  # Run unit tests
  travisFoldStart "test.aio.unit"
    yarn test --single-run
  travisFoldEnd "test.aio.unit"


  # Run unit tests for aio/aio-builds-setup
  travisFoldStart "test.aio.aio-builds-setup"
    ./aio-builds-setup/scripts/test.sh
  travisFoldEnd "test.aio.aio-builds-setup"
)
ci(aio): deploy from CI to staging 2017-01-25 12:39:01 -05:00			`#!/usr/bin/env bash`

ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425) 2017-03-02 03:22:24 -05:00			`set -u -e -o pipefail`
ci(aio): deploy from CI to staging 2017-01-25 12:39:01 -05:00
			`# Setup environment`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`readonly thisDir=$(cd $(dirname $0); pwd)`
			`source ${thisDir}/_travis-fold.sh`


			`# run in subshell to avoid polluting cwd`
			`(`
			`cd ${PROJECT_ROOT}/aio`


			`# Lint the code`
			`travisFoldStart "test.aio.lint"`
ci(aio): verify that the Lighthouse PWA score remains above a threshold 2017-03-31 19:24:25 -04:00			`yarn lint`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`travisFoldEnd "test.aio.lint"`


build(aio): avoid building before running the local PWA tests When this command is run on CI, `yarn build` has already been run, so this was unnecessarily building angular.io again (adding ~4mins to the `aio` job). When this command is run locally, it is most often about testing a new `lighthouse` version/config, so you don't need to build angular.io over and over (and if necessary, one can always run `yarn build` manually). Closes #19633 2017-10-10 05:22:57 -04:00			`# Run PWA-score tests`
			# (Run before unit and e2e tests, which destroy the `dist/` directory.)
			`travisFoldStart "test.aio.pwaScore"`
			`yarn test-pwa-score-localhost`
			`travisFoldEnd "test.aio.pwaScore"`


ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`# Run unit tests`
			`travisFoldStart "test.aio.unit"`
refactor(aio): remove unnecessary `--` from yarn commands 2017-09-23 10:25:11 -04:00			`yarn test --single-run`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`travisFoldEnd "test.aio.unit"`

ci(aio): test aio-builds-setup as part of the `aio` job 2017-03-01 17:39:37 -05:00
			`# Run unit tests for aio/aio-builds-setup`
			`travisFoldStart "test.aio.aio-builds-setup"`
refactor(aio): move scripts into `scripts/` directory 2017-03-07 04:36:41 -05:00			`./aio-builds-setup/scripts/test.sh`
ci(aio): test aio-builds-setup as part of the `aio` job 2017-03-01 17:39:37 -05:00			`travisFoldEnd "test.aio.aio-builds-setup"`
ci: redo how env variables are set and shared in ci to prevent collisions 2017-03-05 04:49:10 -05:00			`)`