ThetaDev/automerge
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity
automerge/scripts/ci/js_tests

14 lines
443 B
Text
Raw Permalink Normal View History

Add a storage-v2 feature flag The new storage implementation is sufficiently large a change that it warrants a period of testing. To facilitate testing the new and old implementations side by side we slightly abuse cargo's feature flags and add a storage-v2 feature which enables the new storage and disables the old storage. Note that this commit doesn't use `--all-features` when building the workspace in scripts/ci/build-test. This will be rectified in a later commit once the storage-v2 feature is integrated into the other crates in the workspace. Signed-off-by: Alex Good <alex@memoryandthought.me>
2022-07-24 22:31:03 +01:00
set -e
Run the js_test in CI We add a script for running the js tests in `scripts/ci/js_tests`. This script can also be run locally. We move the `automerge-js` package to below the `automerge-wasm` crate as it is specifically testing the wasm interface. We also add an action to the github actions workflow for CI to run the js tests.
2021-12-24 23:00:59 +00:00
THIS_SCRIPT=$(dirname "$0");
WASM_PROJECT=$THIS_SCRIPT/../../automerge-wasm;
JS_PROJECT=$THIS_SCRIPT/../../automerge-js;
Add an e2e testing tool for the JS packaging JS packaging is complicated and testing it manually is irritating. Add a tool in `automerge-js/e2e` which stands up a local NPM registry and publishes the various packages to that registry for use in automated and manual tests. Update the test script in `scripts/ci/js_tests` to run the tests using this tool
2022-09-21 22:55:13 +01:00
E2E_PROJECT=$THIS_SCRIPT/../../automerge-js/e2e;
yarn --cwd $E2E_PROJECT install;
# This will build the automerge-wasm project, publish it to a local NPM
# repository, then run `yarn build` in the `automerge-js` directory with
# the local registry
yarn --cwd $E2E_PROJECT e2e buildjs;
yarn --cwd $JS_PROJECT test
Reference in a new issue Copy permalink