Untested:
These methods require an account with zen and it will need to make use of a javascript library such as web3.js to build, sign, and send transactions:
- eth_sendTransaction
- eth_sendRawTransaction
- eth_sign
Issue the following commands:
git clone [email protected]:HorizenOfficial/rpc-tests.git;
cd rpc-tests;
git submodule add --force [email protected]:ethereum/execution-apis.git;
git submodule update --init;
npm install;
cp .env.gobi .env;
These tests require basic auth username and password to be set:
RPC_USERNAME=
RPC_PASSWORD=
These tests require adding 2 Private Keys (PKs) of the sending wallets to the .env as:
SEND_FROM_PK=
SEND_FROM_PK2=
This should not be committed. We use multiple wallets so that nonce values are not confused during parallel testing.
To run EOA to EOA test:
npm run test-gobi rpc/transactions/eoa
To run the tests, ensure .env files exist then execute one of:
npm run test-local
npm run test-pregobi
npm run test-gobi
npm run test-eon
docker build -t rpc-tests .
docker run -v $(pwd)/reports:/usr/src/app/reports rpc-tests npm run test-gobi
You can run tests for a specific RPC namespace such as rpc/eth by issuing the following command:
npm run test rpc/eth;
You can run tests for a specific RPC method such as rpc/eth/feeHistory by issuing the following command:
npm run test rpc/eth/feeHistory
Have a look at the rpc/eth directory for the list of supported RPC methods that can be tested.
You can modify the test parameters and use your own values by modifying the options.params property. For example for the rpc/eth/getBlockByHash method, you will add your parameters like so:
options: {
id: fixtures.id,
jsonrpc: fixtures.jsonrpc,
method: "eth_getBlockByHash",
params: ["0x4a390501c77e6f943a4f8cf69e4c76b426918f357583257df89878a8ef2caa39", true], // add parameters here
},