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
We need a better way of testing changes to the custom reactor code. The simulator should spawn N go-routines to simulate N validators, and then deterministically generate a bunch of random messages (withdrawals in the case of the Gateway reactors) from a seed. Then we can hook this up to a fuzzer that can generated the seeds for the tests.
The text was updated successfully, but these errors were encountered:
We need a better way of testing changes to the custom reactor code. The simulator should spawn N go-routines to simulate N validators, and then deterministically generate a bunch of random messages (withdrawals in the case of the Gateway reactors) from a seed. Then we can hook this up to a fuzzer that can generated the seeds for the tests.
The text was updated successfully, but these errors were encountered: