embark/packages/stack
Michael Bradley, Jr 9f2a5949c2 build: specify missing test action in relevant package.json "qa" scripts
It's a relevant `package.json` if the package has a test suite. If `test` isn't
specified then the tests won't run in CI (they have't been running).

Include a fix for one failing test in `packages/plugins/ens` and two failing
test in `packages/stack/deployment`. In all three cases, the mock embark
object's config needed a `blockchainConfig` section with `{ enabled: true }`.
2019-12-11 14:01:12 -06:00
..
api chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
authenticator chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
blockchain fix(@embark/debugger): Re-enable debugger 2019-12-11 11:12:52 -05:00
blockchain-client chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
communication build: specify missing test action in relevant package.json "qa" scripts 2019-12-11 14:01:12 -06:00
compiler fix(@embark/tests): Tests exiting early 2019-12-11 11:27:45 -05:00
contracts-manager chore(release): 5.0.0-alpha.3 2019-12-06 06:15:07 -05:00
deployment build: specify missing test action in relevant package.json "qa" scripts 2019-12-11 14:01:12 -06:00
embarkjs fix(@embark/blockchain): make disabling blockchain feature work 2019-12-11 11:08:13 -05:00
library-manager chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
namesystem chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
pipeline fix(@embark/blockchain): make disabling blockchain feature work 2019-12-11 11:08:13 -05:00
process-logs-api-manager chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
proxy fix(@embark/test): fix using --node option in tests 2019-12-11 11:05:12 -05:00
storage chore(release): 5.0.0-alpha.3 2019-12-06 06:15:07 -05:00
test-runner fix(@embark/test): fix using --node option in tests 2019-12-11 11:05:12 -05:00
watcher chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00
webserver chore(release): 5.0.0-alpha.2 2019-12-05 15:03:09 -05:00