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
This would also be useful to (in)validate some assumptions we often rely on such as "there is a non-negligeable probability that those 2/3/4 mutations will be jointy applied in one stage".
The text was updated successfully, but these errors were encountered:
Do you envision here more unit/benchmark tests that tests the mutations in isolation, or something more E2E?
I think we want to have some E2E tests at some point to confirm that tlspuffin is still working.
An idea here: We do not test the mutations in isolation and write a dummy PUT that crashes when seeing specific messages. That dummy PUT could be quite simple, but likely would need some decoding and decryption capabilities. Unless we design a non-encrypted and simple protocol that just demos some mutations.
Goal: have a couple of reachability tests of the form
Examples of predicates are:
This would also be useful to (in)validate some assumptions we often rely on such as "there is a non-negligeable probability that those 2/3/4 mutations will be jointy applied in one stage".
The text was updated successfully, but these errors were encountered: