RPC nodes

Steps to run the tests

  1. The RPC nodes' integration tests are disabled by default.
    Remove ./rpc-nodes.spec.ts from "testPathIgnorePatterns" in the package.json.
  2. In the integration test folder, run one of the following commands:
    • Carthagenet: npm run test:carthagenet rpc-nodes.spec.ts
    • Delphinet: npm run test:delphinet rpc-nodes.spec.ts
    • Both protocols: npm run test rpc-nodes.spec.ts

When all endpoints are accessible for a node, you will obtain :

Test calling all methods from RPC node: https://a-node
โœ“ Get the head block hash (1376 ms)
โœ“ List the ancestors of the head block (1010 ms)
โœ“ Access the balance of an address (1024 ms)
โœ“ Access the data of a contract (1022 ms)
โœ“ Access the code and data of a contract (1096 ms)
โœ“ Access the complete status of a contract (1057 ms)
โœ“ Access the manager key of a contract (1023 ms)
โœ“ Access the delegate of a contract (1023 ms)
โœ“ Access the value associated with a key in a big map (3927 ms)
โœ“ Fetches information about a delegate from RPC (1590 ms)
โœ“ Get all constants from RPC (938 ms)
โœ“ Get all the information about a block (1021 ms)
โœ“ Get the whole block header (1125 ms)
โœ“ Get all the metadata associated to the block (918 ms)
โœ“ Retrieves the list of delegates allowed to bake a block (912 ms)
โœ“ Retrieves the list of delegates allowed to endorse a block (971 ms)
โœ“ Get ballots casted so far during a voting period (1059 ms)
โœ“ Get sum of ballots casted so far during a voting period (904 ms)
โœ“ Get current period kind (907 ms)
โœ“ Get current proposal under evaluation (986 ms)
โœ“ Get current expected quorum (920 ms)
โœ“ List of delegates with their voting weight, in number of rolls (923 ms)
โœ“ List of proposals with number of supporters (1023 ms)
โœ“ Forge an operation returning the unsigned bytes (1026 ms)
โœ“ Inject an operation in node and broadcast it (1127 ms)
โœ“ Simulate the validation of an operation (1022 ms)
โœ“ Get the list of entrypoints of the contract (1023 ms)
โœ“ Get chain ID (896 ms)
โœ“ Run an operation without signature checks (948 ms)

Otherwise, you will see which endpoints do not work for a specific node:

Test calling all methods from RPC node: https://another-node
โœ“ Get the head block hash (888 ms)
โœ“ List the ancestors of the head block (782 ms)
โœ“ Access the balance of an address (779 ms)
โœ“ Access the data of a contract (636 ms)
โœ“ Access the code and data of a contract (801 ms)
โœ“ Access the complete status of a contract (638 ms)
โœ“ Access the manager key of a contract (771 ms)
โœ“ Access the delegate of a contract (682 ms)
โœ“ Access the value associated with a key in a big map (4200 ms)
โœ“ Fetches information about a delegate from RPC (739 ms)
โœ“ Get all constants from RPC (633 ms)
โœ“ Get all the information about a block (673 ms)
โœ“ Get the whole block header (648 ms)
โœ“ Get all the metadata associated to the block (646 ms)
โœ“ Retrieves the list of delegates allowed to bake a block (814 ms)
โœ“ Retrieves the list of delegates allowed to endorse a block (649 ms)
โœ• Get ballots casted so far during a voting period (634 ms)
โœ• Get sum of ballots casted so far during a voting period (707 ms)
โœ• Get current period kind (766 ms)
โœ• Get current proposal under evaluation (654 ms)
โœ• Get current expected quorum (639 ms)
โœ• List of delegates with their voting weight, in number of rolls (630 ms)
โœ• List of proposals with number of supporters (699 ms)
โœ“ Forge an operation returning the unsigned bytes (641 ms)
โœ“ Inject an operation in node and broadcast it (655 ms)
โœ“ Simulate the validation of an operation (653 ms)
โœ“ Get the list of entrypoints of the contract (625 ms)
โœ“ Get chain ID (636 ms)
โœ“ Run an operation without signature checks (626 ms)