3afb744e77
Now, running protractor configs by default only runs e2e tests. If the --benchmark flag is added, it runs only the perf tests, and always restarts the browser in between tests. If the --dryrun test is added, the perf tests are run only once. This should make it easier to run perf tests versus example e2e tests, and help stabilize the travis build because perf tests always run with a clean browser.
31 lines
673 B
Bash
Executable File
31 lines
673 B
Bash
Executable File
#!/bin/bash
|
|
set -e
|
|
|
|
echo =============================================================================
|
|
# go to project dir
|
|
SCRIPT_DIR=$(dirname $0)
|
|
cd $SCRIPT_DIR/../..
|
|
|
|
./node_modules/.bin/webdriver-manager update
|
|
|
|
function killServer () {
|
|
kill $serverPid
|
|
}
|
|
|
|
./node_modules/.bin/gulp serve.js.prod&
|
|
serverPid=$!
|
|
|
|
trap killServer EXIT
|
|
|
|
# wait for server to come up!
|
|
sleep 10
|
|
|
|
# Let protractor use default browser unless one is specified.
|
|
OPTIONS="";
|
|
if [[ -n "$E2E_BROWSERS" ]]; then
|
|
OPTIONS="--browsers=$E2E_BROWSERS";
|
|
fi
|
|
|
|
./node_modules/.bin/protractor protractor-js.conf.js $OPTIONS
|
|
./node_modules/.bin/protractor protractor-js.conf.js $OPTIONS --benchmark --dryrun
|