-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
Design a testing framework for Move code #408
Comments
Some non-exhaustive notes on Solidity contract testing frameworks I'm familiar with:
From these, i think we can see that:
|
Another important framework is OpenZepplin, which is the ancestor of DappTools/Foundry.
The audit report provides a nice overview. |
One fundamental limitation in the way we program Move is that, often when you create a new object and transfer it to someone, that object is no longer accessible from Move in the same call. To test something an entire flow of Move code, we need to make several calls to Move (see the hero test in authority_tests). This is inconvenient and not an accessible way of testing application code for Move developers.
We need to come up with a framework that allows Move developers to test that code fully within Move.
The text was updated successfully, but these errors were encountered: