Open Shourya742 opened 1 month ago
We can cover most of the surface, with this combination.
Maker: Normal Taker1: DropConnectionAfterFullSetup Taker2: BroadcastContractAfterFullSetup
These are the only two Taker behaviors we have. And both will force Maker to recover.
Later on, we can add more tests with other Maker behaviors.
In the long term, this can be a good approach to combinatorially cover all weird edge cases.
Add the behaviour for multiple taker to connect to a single chain of makers to perform swap. Use variety of taker behaviour to cover possible cases along with the standard happy path case.
Adds an integration test to simulate this whole situation.