You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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,
The text was updated successfully, but these errors were encountered:
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.
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,
The text was updated successfully, but these errors were encountered: