embark/dapps/tests/app
emizzle 81af3affc4 fix(@embark/tests): Fix failing test with `—node=embark`
## 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`.
2020-01-09 11:41:48 -05:00
..
another_folder build: make DApp templates member packages of the monorepo 2019-03-05 10:20:57 -06:00
app fix(@embark/ens): Show ENS controls for Test DApp 2019-12-17 13:48:06 -05:00
config bugfix (@embark/stack/embarkjs): set default gas so it's an optional parameter for onDeploy directives in the contracts config 2019-11-12 17:08:48 -05:00
some_folder build: make DApp templates member packages of the monorepo 2019-03-05 10:20:57 -06:00
test fix(@embark/tests): Fix failing test with `—node=embark` 2020-01-09 11:41:48 -05:00
.npmrc build: make DApp templates member packages of the monorepo 2019-03-05 10:20:57 -06:00
CHANGELOG.md chore(release): 5.0.0 2020-01-07 12:14:37 -06:00
README.md build: tidy up the monorepo in prep for v5.0.0-alpha.0 2019-10-01 13:29:53 -05:00
embark.json refactor(@embark/library-manager): restrict versionable packages to only solc 2019-11-08 11:27:20 -06:00
package.json chore(release): 5.0.0 2020-01-07 12:14:37 -06:00
test.file build: make DApp templates member packages of the monorepo 2019-03-05 10:20:57 -06:00

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.