2018-05-25 03:17:26 +02:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
|
|
2019-07-09 18:39:31 +02:00
|
|
|
set -x
|
2018-05-25 03:17:26 +02:00
|
|
|
set -e
|
|
|
|
|
set -u
|
|
|
|
|
set -o pipefail
|
|
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry () {
|
|
|
|
|
retry=0
|
|
|
|
|
limit="${METAMASK_E2E_RETRY_LIMIT:-3}"
|
|
|
|
|
while [[ $retry -lt $limit ]]
|
|
|
|
|
do
|
|
|
|
|
"$@" && break
|
|
|
|
|
retry=$(( retry + 1 ))
|
|
|
|
|
sleep 1
|
|
|
|
|
done
|
|
|
|
|
|
|
|
|
|
if [[ $retry == "$limit" ]]
|
|
|
|
|
then
|
|
|
|
|
exit 1
|
|
|
|
|
fi
|
|
|
|
|
}
|
|
|
|
|
|
2018-05-25 03:17:26 +02:00
|
|
|
export PATH="$PATH:./node_modules/.bin"
|
|
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
for spec in test/e2e/tests/*.spec.js
|
|
|
|
|
do
|
|
|
|
|
retry mocha --no-timeouts "${spec}"
|
|
|
|
|
done
|
2020-01-20 19:50:25 +01:00
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry concurrently --kill-others \
|
2019-12-09 15:40:43 +01:00
|
|
|
--names 'dapp,e2e' \
|
2019-07-09 18:39:31 +02:00
|
|
|
--prefix '[{time}][{name}]' \
|
|
|
|
|
--success first \
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
|
|
|
'yarn dapp' \
|
2019-12-09 15:40:43 +01:00
|
|
|
'mocha test/e2e/metamask-ui.spec'
|
2019-07-09 18:39:31 +02:00
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry concurrently --kill-others \
|
2019-12-09 15:40:43 +01:00
|
|
|
--names 'dapp,e2e' \
|
2019-07-09 18:39:31 +02:00
|
|
|
--prefix '[{time}][{name}]' \
|
|
|
|
|
--success first \
|
Switch from `npm` to `yarn` (#6843)
As a solution to the constant lockfile churn issues we've had with
`npm`, the project now uses `yarn` to manage dependencies.
The `package-lock.json` file has been replaced with `yarn.lock`, which
was created using `yarn import`. It should approximate the contents of
`package-lock.json` fairly well, though there may be some changes due to
deduplication. The codeowners file has been updated to reference this
new lockfile.
All documentation and npm scripts have been updated to reference `yarn`
rather than `npm`. Note that running scripts using `npm run` still works
fine, but it seemed better to switch those to `yarn` as well to avoid
confusion.
The `npm-audit` Bash script has been replaced with `yarn-audit`. The
output of `yarn audit` is a bit different than `npm audit` in that it
returns a bitmask to describe which severity issues were found. This
made it simpler to check the results directly from the Bash script, so
the associated `npm-audit-check.js` script was no longer required. The
output should be exactly the same, and the information is still sourced
from the same place (the npm registry).
The new `yarn-audit` script does have an external dependency: `jq`.
However, `jq` is already assumed to be present by another CI script, and
is present on all CI images we use. `jq` was not added to `package.json`
as a dependency because there is no official package on the npm
registry, just wrapper scripts. We don't need it anywhere exept on CI
anyway.
The section in `CONTRIBUTING` about how to develop inside the
`node_modules` folder was removed, as the advice was a bit dated, and
wasn't specific to this project anyway.
2019-07-30 20:36:23 +02:00
|
|
|
'yarn dapp' \
|
2019-12-09 15:40:43 +01:00
|
|
|
'mocha test/e2e/metamask-responsive-ui.spec'
|
2019-07-09 18:39:31 +02:00
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry concurrently --kill-others \
|
2019-12-09 15:40:43 +01:00
|
|
|
--names 'e2e' \
|
2019-07-09 18:39:31 +02:00
|
|
|
--prefix '[{time}][{name}]' \
|
|
|
|
|
--success first \
|
2019-12-09 15:40:43 +01:00
|
|
|
'mocha test/e2e/from-import-ui.spec'
|
2019-07-31 21:56:44 +02:00
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry concurrently --kill-others \
|
2019-12-09 15:40:43 +01:00
|
|
|
--names 'sendwithprivatedapp,e2e' \
|
2019-08-02 05:57:26 +02:00
|
|
|
--prefix '[{time}][{name}]' \
|
|
|
|
|
--success first \
|
2020-02-06 16:52:40 +01:00
|
|
|
'yarn sendwithprivatedapp' \
|
2019-12-09 15:40:43 +01:00
|
|
|
'mocha test/e2e/incremental-security.spec'
|
2019-08-03 01:00:50 +02:00
|
|
|
|
2020-07-24 00:31:42 +02:00
|
|
|
retry concurrently --kill-others \
|
2019-12-09 15:40:43 +01:00
|
|
|
--names '3box,dapp,e2e' \
|
2019-10-31 17:27:22 +01:00
|
|
|
--prefix '[{time}][{name}]' \
|
|
|
|
|
--success first \
|
|
|
|
|
'node test/e2e/mock-3box/server.js' \
|
|
|
|
|
'yarn dapp' \
|
2019-12-09 15:40:43 +01:00
|
|
|
'mocha test/e2e/threebox.spec'
|
