Separated network tests: network-tests.js. They will run every Monday.
Deployed sample contract on all testnets and used existing contracts with immutables in our repo when found.
Also found out some errors in immutable verification with scraping: different regex in Avax Fuji, URL typo in Arbitrum; sometimes scraping encounters CAPTCHA as in Binance Testnet. Added error logging for when it sees CAPTCHA.
With the new test structure an automated process for adding networks
The chain support PR now must include test contracts added to the network-tests.js (ideally a normal contract + immutable)
The branch must be named in add-network-{chainId} format. With that, the network-tests.js for only the {chainId} will run. We are not going to have to test manually. (example xDai (100))
With the new test structure it should be possible to dynamically display which network is successfully running + which network supports immutables on the "network support" table
Figured out it was a bit messed with the Ethereum RPCs: We had dappnode + INFURA_ID but weren't used. Also many Alchemy IDs but not all used. Once we have an extended tier from Alchemy, will consolidate into a single Alchemy ID.
network-tests.js(ideally a normal contract + immutable)add-network-{chainId}format. With that, thenetwork-tests.jsfor only the{chainId}will run. We are not going to have to test manually. (example xDai (100))Upcoming: