Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: mock-upstream-provider to replace alchemy in testing (fails intermittently) #57

Open
sabotagebeats opened this issue May 11, 2022 · 1 comment
Labels
category: feature New feature or request

Comments

@sabotagebeats
Copy link
Contributor

mock-upstream-provider. We can just statically feed the state this way, no HTTP required

  • What you are trying to do
    use tests that rely on alchemy in ape
  • Why Ape's current functionality is inadequate to address your goal
    alchemy fails intermittently when testing
@sabotagebeats sabotagebeats added the category: feature New feature or request label May 11, 2022
@antazoey
Copy link
Contributor

I think after this exists: ApeWorX/ape#680, we can create a .db full of data for mainnet-fork and then include that file in the tests and run with that latest block number as the arg.

Then, it does not need to rely on Alchemy so much and we focus on the plugin.
I think we also need to chat with Alchemy about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants