element-web/scripts/ci/app-tests.sh

#!/bin/bash
#
# script which is run by the CI build (after `yarn test`).
#
# clones element-web develop and runs the tests against our version of react-sdk.

set -ev

scripts/ci/layered.sh
cd ../element-web
yarn build:genfiles # so the tests can run. Faster version of `build`
yarn test
run both react-sdk and riot-web tests 2019-01-09 17:16:20 +03:00			`#!/bin/bash`
			`#`
Add basic BuildKite :pipeline: 2019-03-14 02:42:05 +03:00			# script which is run by the CI build (after `yarn test`).
run both react-sdk and riot-web tests 2019-01-09 17:16:20 +03:00			`#`
Rebrand various CI scripts and modules This replaces Riot with Element in various CI scripts, modules, parameters, etc. This _should_ be the last major rebranding pass (hopefully). Fixes https://github.com/vector-im/element-web/issues/14894 2020-12-03 16:56:27 +03:00			`# clones element-web develop and runs the tests against our version of react-sdk.`
run both react-sdk and riot-web tests 2019-01-09 17:16:20 +03:00
			`set -ev`

Rebrand various CI scripts and modules This replaces Riot with Element in various CI scripts, modules, parameters, etc. This _should_ be the last major rebranding pass (hopefully). Fixes https://github.com/vector-im/element-web/issues/14894 2020-12-03 16:56:27 +03:00			`scripts/ci/layered.sh`
			`cd ../element-web`
Ensure generated files are present for riot-web tests 2020-01-21 20:53:17 +03:00			yarn build:genfiles # so the tests can run. Faster version of `build`
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best. 2019-03-11 17:22:02 +03:00			`yarn test`