Closed ggutoski closed 4 months ago
In all malicious tests (not just type-7) now that we've collapsed all protocol faults into a single catch-all ProtocolFault
enum variant we have no programmatic way to ensure that the intended code path was actually visited---you need to check the test logs to see it.
Looks like we're missing tests for the following code paths:
I vaguely remember from long ago that it was difficult to make a malicious party hit these code paths without also triggering any earlier sad paths.