element-web/scripts/ci/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/build.sh
CHROME_BIN='/usr/bin/google-chrome-stable' yarn test
split up script for unit and end-to-end tests so unit tests are not run as part of e2e tests 2019-01-09 13:21:45 +00:00			`#!/bin/bash`
			`#`
Add basic BuildKite :pipeline: 2019-03-13 23:42:05 +00:00			# script which is run by the CI build (after `yarn test`).
split up script for unit and end-to-end tests so unit tests are not run as part of e2e tests 2019-01-09 13:21:45 +00:00			`#`
			`# clones riot-web develop and runs the tests against our version of react-sdk.`

			`set -ev`

Add basic BuildKite :pipeline: 2019-03-13 23:42:05 +00:00			`scripts/ci/build.sh`
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 14:22:02 +00:00			`CHROME_BIN='/usr/bin/google-chrome-stable' yarn test`