types are not re-generated when "hardhat test" is executed

[drortirosh]

hardhat compile automatically does generate types on every change, but hardhat test doesn't. There is a workaround (always run hardhat compile && hardhat test) but its awkward..

[NikolaiSch]

This is to do with hardhat, not typechain. Other workarounds include:

• creating an alias for hardhat compile && hardhat test in os
• creating a npm / yarn script that named test and then call it using npm run test

[drortirosh]

Yes, this is not a problem of typechain per se, but the hardhat-typechain plugin. The plugin automatically generates types on hardhat compile task, but doesn't automatically generate types on hardhat test

[zemse]

Regenerating types make sense when the artifacts change and they do when you run compile script (which change artifacts only if you change solidity files).

The test script also runs compile script if you changed solidity files else it does not. Are you saying this doesn't happen for you?

[krzkaczor]

@drortirosh @NikolaiSch can you guys prepare an example repo where this happens? This must be a regression because it works. We even have tests for that: https://github.com/dethcrypto/TypeChain/blob/master/packages/hardhat/test/project.test.ts#L77

[startswithaj]

I'm having this same problem:

1. Make a change to a solidity file that fixes a bug, save.
2. Run hardhat test - test fails
3. Run hardhat test again, test passes.

I heavily use the TypeChain factories in my tests, it seems the old types/artifacts are already loaded into memory - the factories include the bytecode from the previous compile, they don't use the bytecode from the artifacts from the compile that executes during hardhat test.