Skip to content

Latest commit

 

History

History
 
 

e2e

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
framework
framework
 
 
README.md
README.md
 
 
discovery_test.go
discovery_test.go
 
 
transaction_test.go
transaction_test.go
 
 
txpool_test.go
txpool_test.go
 
 
websocket_test.go
websocket_test.go
 
 

README.md

E2E tests

The implemented E2E tests start a local instance of polygon-edge.

Step 1: Run the tests

Use the make file to launch the tests make test-e2e-legacy

Manual checks if things are acting funny

Check if the polygon-edge process is running

If you've stopped the tests abruptly, chances are the polygon-edge process is still running on your machine. <br/ > In order for the tests to function normally, please kill the possible remaining processes using killall polygon-edge

Clean the golang test cache

Golang caches test results, and may not even run a test, causing tests to fail on some machines and work on others.

go clean -testcache

This command cleans the test cache, and should be added to the runtime config.

Another way to disable test caching altogether is to add the following flag when running go test -count=1:

go test ./... -count=1

Note

constants

Constant values that used in some e2e tests are defined in e2e/const.go. Mock contract are pre-compiled and the result is stored in const.go in order to avoid dependencies of solc command (solidity compiler).

You can get the byte code from original program by following command.

$ solc --bin e2e/sample.sol

Currently you need to build with version 0.5.x compiler. You can check the compiler version by solc --version.

$ solc --version
solc, the solidity compiler commandline interface
Version: 0.5.17+commit.d19bba13.Darwin.appleclang