c08403935f
Originally we ran gulp enforce-format at the beginning of the build. This was annoying because you came back from lunch to find that no tests ran so you have to start your PR over. Then we changed it to run the linters at the end. This is annoying because you might be ready to merge to master, and could have fixed the lint issues immediately, but now much wait for another PR. The solution is to run the lint checks in another build. This marks your PR red very early, but you still get the feedback of whether the tests are passing.
18 lines
560 B
Bash
Executable File
18 lines
560 B
Bash
Executable File
#!/bin/bash
|
|
set -e
|
|
|
|
echo =============================================================================
|
|
# go to project dir
|
|
SCRIPT_DIR=$(dirname $0)
|
|
cd $SCRIPT_DIR/../..
|
|
|
|
# Issue #945 Travis still uses Dartium, and hence needs the env setup.
|
|
# For local tests, when a developer doesn't have Dart, don't source env_dart.sh
|
|
if ${SCRIPT_DIR}/env_dart.sh 2>&1 > /dev/null ; then
|
|
source $SCRIPT_DIR/env_dart.sh
|
|
fi
|
|
|
|
./node_modules/.bin/gulp pre-test-checks
|
|
./node_modules/.bin/gulp test.js --browsers=${KARMA_BROWSERS:-ChromeCanary}
|
|
${SCRIPT_DIR}/test_e2e_js.sh
|