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

Consider proptest and libfuzzer for testing contracts #359

Open
hashedone opened this issue Jul 28, 2021 · 2 comments
Open

Consider proptest and libfuzzer for testing contracts #359

hashedone opened this issue Jul 28, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@hashedone
Copy link
Contributor

I think it would benefit on fuzztest and property test of contracts.

The fuzztests addresses the issue, that when contract crashes, the error message turns out not being nice. Detecting potential crashes early and having example how to integrate those to new contracts, so it would be easier to handle this kind of ptoblems.

Proptest is just a way to slightly generalize tests to easier find bugs in edge cases,

@hashedone hashedone added the enhancement New feature or request label Jul 28, 2021
@ethanfrey
Copy link
Member

Once we have good unit test setup (pretty good now) and complete multi-test coverage (on our way to do that), I think some automated test tooling would be a good place to invest time.

I like proptest/quicktest style checks. We can just focus on manually testing the business logic for "good" and "fail" cases, and let these automated tools try to find some edge case we missed. It would be great to try this out on a contract and find some best practices and add some docs on how to do so.

@ethanfrey
Copy link
Member

Let's at least investigate this as part of v0.12 while adding some code coverage to the CI #172

We can always punt it to v0.13 or later, but adding to the milestone so we investigate it a bit.

@ethanfrey ethanfrey added this to the v0.12.0 milestone Dec 14, 2021
@maurolacy maurolacy self-assigned this Apr 5, 2022
@maurolacy maurolacy removed their assignment Aug 8, 2022
@uint uint removed this from the v0.12.0 milestone Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants