-
Notifications
You must be signed in to change notification settings - Fork 91
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
refactor: remove CreditNft mock #762
refactor: remove CreditNft mock #762
Conversation
are we purging many of the mocks contracts if not all? @rndquu |
You're right, mocks make unit tests easier. On the frontend, for example, you can mock API calls. On the backend, for example, you can mock DB queries. But in the contracts it is not a big deal to deploy everything you need locally. Check the mocks folder. It arises a question:
I understand why Curve's contracts were mocked (because they should be compiled with vyper and it is tricky to set it up in foundry) but other contract should not have been mocked. Your mock implementation can differ from a real contract hence there might be errors in unit tests while using the real contracts make sure that everything will work fine in production. |
I agree in testing real contracts on forked chain than having mocks and mocks for each update |
This PR:
CreditNft
mock contractCreditNft
contract