We need a flow chart of the execute method for the FilibusterGrpcTest. We should write this down as an outline before diagramming it to make sure.
It needs to be abstract enough that it can fit on a page and be clear, but detailed enough that we should be able to map each of our new subclass extensions into it.
The easiest way to construct this is probably to think about the testing passes and how the system address them:
For example:
[ ] Reference Execution
[ ] Reference Execution with Stub/Verify Checking
[ ] Single Fault Execution, for injected fault
[ ] Verify that the user specified the behavior when fault injected
[ ] Verify that the user specified behavior is correct
[ ] Effectively all these do is allow us to change the assertion block with shorthands for writing new assertion blocks with differential for stub assertions.
[ ] No effect, normal assertions (no assertion impact)
We need a flow chart of the execute method for the FilibusterGrpcTest. We should write this down as an outline before diagramming it to make sure.
It needs to be abstract enough that it can fit on a page and be clear, but detailed enough that we should be able to map each of our new subclass extensions into it.
The easiest way to construct this is probably to think about the testing passes and how the system address them:
For example: