element-web/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

RIOT_WEB_DIR=riot-web

scripts/ci/build.sh
pushd "$RIOT_WEB_DIR"
yarn test
popd
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			`#`
			`# clones riot-web develop and runs the tests against our version of react-sdk.`

			`set -ev`

			`RIOT_WEB_DIR=riot-web`

Add basic BuildKite :pipeline: 2019-03-14 02:42:05 +03:00			`scripts/ci/build.sh`
run both react-sdk and riot-web tests 2019-01-09 17:16:20 +03:00			`pushd "$RIOT_WEB_DIR"`
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`
run both react-sdk and riot-web tests 2019-01-09 17:16:20 +03:00			`popd`