metamask-extension/test/run-jest.sh

#!/usr/bin/env bash

set -x
set -e
set -u
set -o pipefail

concurrently \
  "jest --config=./jest.config.js $*" \
  "jest --config=./development/jest.config.js $*"
Add build-time code exclusion using code fencing (#12060) This PR adds build-time code exclusion by means of code fencing. For details, please see the README in `./development/build/transforms`. Note that linting of transformed files as a form of validation is added in a follow-up, #12075. Hopefully exhaustive tests are added to ensure that the transform works according to its specification. Since these tests are Node-only, they required their own Jest config. The recommended way to work with multiple Jest configs is using the `projects` field in the Jest config, however [that feature breaks coverage collection](https://github.com/facebook/jest/issues/9628). That being the case, I had to set up two separate Jest configs. In order to get both test suites to run in parallel, Jest is now invoked via a script, `./test/run-jest.sh`. By way of example, this build system feature allows us to add fences like this: ```javascript this.store.updateStructure({ ..., GasFeeController: this.gasFeeController, TokenListController: this.tokenListController, ///: BEGIN:ONLY_INCLUDE_IN(beta) PluginController: this.pluginController, ///: END:ONLY_INCLUDE_IN }); ``` Which at build time are transformed to the following if the build type is not `beta`: ```javascript this.store.updateStructure({ ..., GasFeeController: this.gasFeeController, TokenListController: this.tokenListController, }); ``` Co-authored-by: Mark Stacey <markjstacey@gmail.com> 2021-09-14 19:00:04 +02:00			`#!/usr/bin/env bash`

			`set -x`
			`set -e`
			`set -u`
			`set -o pipefail`

			`concurrently \`
			`"jest --config=./jest.config.js $*" \`
			`"jest --config=./development/jest.config.js $*"`