ci(aio): run e2e tests in `production` mode (#21470)

This will enable catching errors introduced by build optimizations that
do not appear in `development` mode.

Fixes #21446

PR Close #21470
This commit is contained in:
George Kalpakas 2018-01-11 15:40:27 +02:00 committed by Alex Eagle
parent 05208b8513
commit f6db9521ab
2 changed files with 3 additions and 1 deletions

View File

@ -19,6 +19,7 @@
"test": "yarn check-env && ng test",
"pree2e": "yarn check-env && yarn ~~update-webdriver",
"e2e": "ng e2e --no-webdriver-update",
"e2e-prod": "yarn e2e --environment=dev --target=production",
"preinstall": "node ../tools/yarn/check-yarn.js",
"presetup": "yarn install --frozen-lockfile && yarn ~~check-env && yarn boilerplate:remove",
"setup": "yarn aio-use-npm && yarn example-use-npm",

View File

@ -33,7 +33,8 @@ source ${thisDir}/_travis-fold.sh
# Run e2e tests
travisFoldStart "test.aio.e2e"
yarn e2e
# Use `production` mode to catch issues introduced by build optimizations.
yarn e2e-prod
travisFoldEnd "test.aio.e2e"