This issue is also being tracked on Linear.

We use Linear to manage our development process, but we keep the conversations on Github.

LINEAR-ID: 76fbcb73-8707-4c4e-a9b0-d45fce9a2b58

This issue was marked as stale because it didn't have any activity in the last 30 days. If you think it's still relevant, please leave a comment indicating so. Otherwise, it will be closed in 7 days.

This issue was closed because it has been stalled for 7 days with no activity.

Hi @fvictorio , Can you please assign this issue to me? Thanks.

Done! Let me know if you need help.

Hi @fvictorio , I have made a pull request for it. You can have a look. Thanks.

#3825 better message when url is an empty string.

Hello @fvictorio, I'm looking at the list of good first issues and am interested in taking a stab at this issue if its okay.

P.S. your evm-puzzles were really helpful in making me understand evm at a practical level :)

I have a question, am trying to run tests in the hardhat-core package. It's requiring me both ALCHEMY_URL and INFURA_URL.

I've added a file packages/hardhat-core/.env and populated with the following, but still shows the same error.

INFURA_URL=https://sepolia.infura.io/v3/[REDACTED]
ALCHEMY_URL=https://eth-sepolia.g.alchemy.com/v2/[REDACTED]

• Where should I be setting the environment variables?
• And is using Sepolia HTTP url correct, or should I use another network (Mainnet, Goerli, etc.)?

EDIT:

• Was able to run the tests by exporting variables to my cli export ALCHEMY_URL=...
• Have used mainnet rpc urls after seeing tests fail on Sepolia rpc. Might be obvious, but wasn't clear to me as a first time potential contributor.

Hey @kshyun28, sorry for not responding sooner and thanks for the PR!

Have used mainnet rpc urls after seeing tests fail on Sepolia rpc. Might be obvious, but wasn't clear to me as a first time potential contributor.

That's a great point. Do you want to send a separate PR improving that warning? Ideally we would change the environment variables names too, but that will be a huge change and maybe it's not worth it

your evm-puzzles were really helpful in making me understand evm at a practical level

Super glad to read that 😄

That's a great point. Do you want to send a separate PR improving that warning? Ideally we would change the environment variables names too, but that will be a huge change and maybe it's not worth it

I'm okay with sending an additional PR to improve the warning message. Currently I'm thinking TEST RUN INCOMPLETE: You need to define the env variable INFURA_URL to an Ethereum mainnet HTTP provider

I'd also suggest to add a section in CONTRIBUTING.md on configuring environment variables for tests as needed. A note/hint could work, since I only knew that environment variables are needed after attempting to run the test.

Might have to review if steps to configure env variables are the same in windows, but export VARIABLE=value should work on mac/linux.

CONTRIBUTING.md

## Testing 

All tests are written using [mocha](https://mochajs.org) and [chai](https://www.chaijs.com).

### Environment variables

Some tests require having `INFURA_URL` and `ALCHEMY_URL` configured. 
You can set them in your terminal using `export ALCHEMY_URL=value INFURA_URL=value`.

### Per-package

You can run a package's tests by executing `yarn test` inside its folder.

### Entire project

You can run all the tests at once by running `yarn test` from the root folder.