-
Notifications
You must be signed in to change notification settings - Fork 2
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
How to run the tests #4
Comments
The tests are run from ClarityTools. There are two levels of tests: 1. Tests during development. Tests run during development are integrated in the source code for the library. Note that these source files are written in a superset of the Clarity language, which is supported and transpiled by ClarityTools. To see in action, open a source file in ClarityTools. The 2. Tests after deployment. There are also tests to check the expected responses from calling functions in deployed contracts. Any of the source files can be transpiled into vanilla Clarity and deployed from ClarityTools. The functions in the deployed contracts can then be called from their respective ClarityTools test contract, which optionally can be transpiled and deployed for on-chain testing. |
Thank you! I like the idea of having the tests written in Clarity. If I run into any edge cases or bugs, I will report them here. I will use those contracts to test the fuzzing tool I'm working on. I just tested
Smaller inputs (expand for more)
|
In the same context, |
Great work 🚀 How do you run the tests? I'd like to do some property-based/fuzz testing with the clarinet tooling I'm working on. (It's internal for now, but part of it is described in hirosystems/clarinet#398.)
The text was updated successfully, but these errors were encountered: