You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the plan is to have an automated test that at some frequency will declare/deploy new accounts on sepolia, it is necessary to secure an account that will always have SepoliaETH on it so that the funding step in test case workflow will not fail. Therefore, it needs to be investigated how public/private key is going to be integrated in workflow. Additionally, it could be investigated how to automatically fund the account from the faucets so that it won't dry out.
The text was updated successfully, but these errors were encountered:
Since the plan is to have an automated test that at some frequency will declare/deploy new accounts on sepolia, it is necessary to secure an account that will always have SepoliaETH on it so that the funding step in test case workflow will not fail. Therefore, it needs to be investigated how public/private key is going to be integrated in workflow. Additionally, it could be investigated how to automatically fund the account from the faucets so that it won't dry out.
The text was updated successfully, but these errors were encountered: