9202cce3f5
Switch the activity filter to use the new session-based API that deliver incremental updates to the current filter. Drop the old quick win listening for individual change events and use the unified API instead. The new transactions (on-top) trigger the old "new transactions" buttons that trigger reset of the current filter and the top new transacitons highlighted. Highlight mixed changes (not new on top) as they come in Highlight new changes on filter reset Closes #12120 |
||
---|---|---|
.. | ||
helpers | ||
wallet | ||
.gitignore | ||
README.md | ||
go.mod | ||
go.sum | ||
integration_tests_config-template.json |
README.md
Development integration tests for status-go
These integration tests are an experiment. They rely on an existing developer environment (working user folder, blockchain access tokens) and internet connection.
If it proves its usefulness we might consider automating them and make it independent of internet services
How to run tests
Setup steps
- Dump the node config passed to
Login
status-go call as.node_config.json
and use its path later on in asnodeConfigFile
in.integration_tests_config.json
- Ensure the blockchain access tokens are configured when dumping the configuration file
- Copy integration_tests_config-template.json to tests sub-folders and rename it as
.integration_tests_config.json
, then update it with your own values.- Update
nodeConfigFile
with the previously extracted node config path - The
hashedPassword
should be the "0x" +keccak256(clearPassword)
- For
dataDir
it is expected an working status-go user folder (e.g. the usualstatus-desktop/Second/data
used withmake run
command)
- Update
Run wallet tests
-
once
(cd test/status-go/integration && go test -count=1 -v ./wallet/... --tags=gowaku_no_rln,gowaku_skip_migrations)
-
continuously on code changes
(cd test/status-go/integration && nodemon --watch ../../../vendor/status-go/ --watch . --ext "*.go,*.sql" --exec 'go test -count=1 -v ./wallet/... --tags=gowaku_no_rln,gowaku_skip_migrations 2>&1 | tee ~/proj/tmp/status-go-tests.log || exit 1')