The Status module that consumes go-ethereum
https://status.im
281b304edb
This change moves our e2e tests into a separate package to make room for proper unit and integration tests. This is Phase 1 described in #371. Changes: Makefile has separate directives to run unit/integration tests and e2e tests, CI runs unit/integration tests first and then e2e tests, E2e tests are in reliability order, i.e. the least reliable tests are run in the end to be sure that nothing else is broken, Some tests are fixed or quarantined. |
||
---|---|---|
.github | ||
build | ||
cmd/statusd | ||
e2e | ||
extkeys | ||
geth | ||
helpers/profiling | ||
static | ||
testing | ||
vendor | ||
xgo | ||
.dockerignore | ||
.gitignore | ||
.travis.yml | ||
Dockerfile | ||
Jenkins-manual | ||
Jenkinsfile | ||
LICENSE.md | ||
Makefile | ||
README.md | ||
package.json |
README.md
Status bindings for go-ethereum
Docs
Intro
status-go is an underlying part of Status - a browser, messenger, and gateway to a decentralized world.
It's written in Go and requires Go 1.8 or above.
It uses Makefile to do most common actions. See make help
output for available commands.
status-go uses forked ethereum-go with some changes in it, located under vendor/
dir.
Build
There are two main modes status-go can be built:
- standalone server
- library to link for Android or iOS
Use following Makefile commands:
make statusgo
(builds binary intobuild/bin/statusd
)make statusgo-android
) (builds .aar filebuild/android-16/aar
)make statusgo-ios
andmake statusgo-ios-simulator
(builds iOS related artifacts inbuild/os-9.3/framework
)
Testing
To test statusgo, use: make ci
.
If you want to launch specific test, for instance RPCSendTransactions
, use the following command:
./build/env.sh go test -v ./geth/api/ -testify.m ^RPCSendTransaction$
Note -testify.m
as testify/suite is used to group individual tests.