ci(aio): verify that the Lighthouse PWA score remains above a threshold

This commit is contained in:
Georgios Kalpakas
2017-04-01 02:24:25 +03:00
committed by Pete Bacon Darwin
parent a73050de48
commit 49d97e1216
8 changed files with 366 additions and 19 deletions

View File

@ -71,7 +71,7 @@ case ${CI_MODE} in
;;
0)
# Preconditions met: Deploy
yarn run deploy-preview
yarn deploy-preview
;;
esac
fi
@ -82,7 +82,7 @@ case ${CI_MODE} in
else
# This is upstream master: Deploy to staging
travisFoldStart "deploy.aio.staging"
yarn run deploy-staging
yarn deploy-staging
travisFoldEnd "deploy.aio.staging"
fi
)

View File

@ -58,6 +58,12 @@ if [[ ${TRAVIS:-} ]]; then
browserstack_optional)
setEnvVar KARMA_JS_BROWSERS `node -e "console.log(require('/home/travis/build/angular/angular/browser-providers.conf').browserstackAliases.CI_OPTIONAL.join(','))"`
;;
aio)
# Due to network latency/server performance, the min accepted PWA score
# on previews is a little lower than on staging.
setEnvVar MIN_PWA_SCORE_PREVIEW 93
setEnvVar MIN_PWA_SCORE_STAGING 95
;;
esac
else
setEnvVar KARMA_JS_BROWSERS Chrome

View File

@ -14,7 +14,7 @@ source ${thisDir}/_travis-fold.sh
# Lint the code
travisFoldStart "test.aio.lint"
yarn run lint
yarn lint
travisFoldEnd "test.aio.lint"
@ -34,10 +34,16 @@ source ${thisDir}/_travis-fold.sh
# Run e2e tests
travisFoldStart "test.aio.e2e"
yarn run e2e
yarn e2e
travisFoldEnd "test.aio.e2e"
# Run PWA-score tests
travisFoldStart "test.aio.pwaScore"
yarn test-pwa-score-local
travisFoldEnd "test.aio.pwaScore"
# Run unit tests for aio/aio-builds-setup
travisFoldStart "test.aio.aio-builds-setup"
./aio-builds-setup/scripts/test.sh