Hardhat Chain Fork Testing – How to Execute on Test Rather Than Config File

hardhatsoliditytesting

I saw that it is possible to test with Hardhat on a forked chain, via the config file.

Is it possible to do it on the test file instead? In a beforeEach, maybe.

I only want some of my tests to run on a fork, while the majority should just run on the normal test network.

Best Answer

yes

just change your network (add this with your api key to the before each):

await hre.network.provider.request({
      method: "hardhat_reset",
      params: [{forking: {
            jsonRpcUrl: "https://eth-mainnet.alchemyapi.io/v2/xxxxxx",
            blockNumber:14768690
          },},],
      });

Related Solutions

testing – Using Fork on Hardhat in Testing: A Comprehensive Guide

Afaik hardhat test spins up their own test network, unless you specify it in the hardhat config.

Alternatively you should be able specify explicitly that hardhat should use your local hardhat node (e.g. http://localhost:8545) by adding --network localhost. See https://hardhat.org/hardhat-network/#running-stand-alone-in-order-to-support-wallets-and-other-software

Hardhat – How to Read Config Programmatically at Runtime and Log Attributes

Great question; try something like this:

Use hre.network.config.url;

Here is an example of how you can get the RPC Provider URL at runtime in your deploy.js script:

const hre = require("hardhat");

console.log("provider url: ", hre.network.config.url);

So then, for example if you run the deploy locally, the provider URL might be undefined:

% npx hardhat run scripts/deploy.js
provider url:  undefined

But if you switch to a network that you have defined, you will then see the api provider URL:

% npx hardhat run scripts/deploy.js --network rinkeby
provider url:  https://eth-rinkeby.alchemyapi.io/v2/<api-key>

Best Answer

Related Solutions

testing – Using Fork on Hardhat in Testing: A Comprehensive Guide

Hardhat – How to Read Config Programmatically at Runtime and Log Attributes

Related Topic