iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/scripts/ci/test_js.sh

18 lines
558 B
Bash
Raw Normal View History

chore(test): make it easier to run all JS and Dart tests Performed a slight refactoring of CI scripts to make it easier for developers to run the **same** tests as those run on Travis. Defined `npm` scripts `test-js` and `test-dart`. `npm test` now runs the whole lot. Closes #966
2015-03-15 16:51:41 -04:00
#!/bin/bash
build(ci): turn on debugging output for ci scripts Closes #5018
2015-11-05 11:20:13 -05:00
set -ex
chore(test): make it easier to run all JS and Dart tests Performed a slight refactoring of CI scripts to make it easier for developers to run the **same** tests as those run on Travis. Defined `npm` scripts `test-js` and `test-dart`. `npm test` now runs the whole lot. Closes #966
2015-03-15 16:51:41 -04:00
echo =============================================================================
# go to project dir
SCRIPT_DIR=$(dirname $0)
cd $SCRIPT_DIR/../..
chore(install+test): single cmd to full install/test & test JS w/o Dart * `npm install` now does a full install; auxiliary installation steps have been integrated into the `postinstall` script. * Updated developer docs `DEVELOPER.md` accordingly; also added instructions to dev docs for performing full tests (via `npm test`) -- same as those run on Travis. * Reorg in tests so that JS tests can run without a Dart env. Partly fixes #945 **under the assumption that when running JS tests locally, `ChromeCanary` is the desired browser to use**. Note that CI tests (Travis) still uses `DartiumWithWebPlatform` across the board (Maybe because ChromeCanary isn't being installed?) Fixes #1012. Closes #1010
2015-03-19 14:36:27 -04:00
# 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
build(gulp/travis): move circular check and style check to before pre/post-test tasks In order to speedup the startup time of test.unit.js task, we are moving the circular dependency check into a pre-test check that executes only on travis. Similarly we are moving the style check to a post-test check that executes on travis. This way if a circular dependency issue occurs, we find it before running tests on CI and if the code is not formatted we fail the build only if all the tests pass. Related to #2536 Related to #2094
2015-06-23 13:36:54 -04:00
./node_modules/.bin/gulp pre-test-checks
chore(build): use Chromium in Travis for JS tests
2015-11-19 17:37:55 -05:00
./node_modules/.bin/gulp test.js --browsers=${KARMA_JS_BROWSERS:-Chrome}
chore(test): make it easier to run all JS and Dart tests Performed a slight refactoring of CI scripts to make it easier for developers to run the **same** tests as those run on Travis. Defined `npm` scripts `test-js` and `test-dart`. `npm test` now runs the whole lot. Closes #966
2015-03-15 16:51:41 -04:00
${SCRIPT_DIR}/test_e2e_js.sh