mirror of https://github.com/embarklabs/embark.git
81af3affc4
## Problem When using `embark test —node=embark` with the test app, the test that listens for contract events would always fail after timing out. Funnily enough, after the timeout, the subsequent test would run, executing a method that would ulimately fire the event listened for in the previous test, causing the second test to fail as well. ## Solution (workaround) Update the contract events listener test in the test app to execute the `set2` method twice, successfully working around the issue. ## NOTES The cause of the issue is unknown and why the workaround works is also unknown. This change works with both `embark test` and `embark test —node=embark`. |
||
---|---|---|
.. | ||
another_folder | ||
app | ||
config | ||
some_folder | ||
test | ||
.npmrc | ||
CHANGELOG.md | ||
README.md | ||
embark.json | ||
package.json | ||
test.file |
README.md
embark-dapp-test-app
Test DApp for integration testing purposes
In the top-level of the monorepo
yarn globalize
to make development embark available on the global PATH.
In this directory
embark run
to check if everything is behaving as expected.
embark test
to see tests are working as expected.
Visit embark.status.im to get started with Embark.