element-web-Github/scripts/ci/riot-unit-tests.sh

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

set -ev

scripts/ci/layered-riot-web.sh
cd ../riot-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 22:16:20 +08:00			`#!/bin/bash`
			`#`
Add basic BuildKite :pipeline: 2019-03-14 07:42:05 +08:00			# script which is run by the CI build (after `yarn test`).
run both react-sdk and riot-web tests 2019-01-09 22:16:20 +08:00			`#`
			`# clones riot-web develop and runs the tests against our version of react-sdk.`

			`set -ev`

Fix layering of the riot-web tests pipeline 2020-01-21 07:12:59 +08:00			`scripts/ci/layered-riot-web.sh`
			`cd ../riot-web`
Ensure generated files are present for riot-web tests 2020-01-22 01:53:17 +08: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 22:22:02 +08:00			`yarn test`