You can combine the model with property-based testing of that code to essentially try your model on the code and vice versa. You might also encode some of your

You can combine the model with property-based testing of that code to essentially try your model on the code and vice versa. You might also encode some of your expectations in there as preconditions, invariants, or postconditions that are checked at runtime during the tests. Throw a fuzzer like AFL at them. Hwayne has write-ups on both of those concepts: learntla.com https://hillelwayne.com/post/pbt-contracts/ https://hillelwayne.com/post/pbt-contracts/ Here's one on contracts that even your management might like: https://www.win.tue.nl/~wstomv/edu/2ip30/references/design-by-contract/index.html https://www.win.tue.nl/~wstomv/edu/2ip30/references/design-b...