> mapping out "given this scenario, x, y and z happen".
I've used scenario tables in some contracts. Each row is a scenario. For each scenario, there are columns for Plan A, Plan B, and Plan C. (Some column entries for a given scenario might be blank.)
Having a contract validation test would be a worthy exercise for the party who didn't write the contract.
This sounds like a great service opportunity for startup/employee contract lawyers... if contracts are like code, then a parser (or maybe legal code pretty-printer) could easily allow a skilled professional to sift through code. Even easier if the contract is standard for a large company.
Not necessarily actually testing (as in, let's go to court) but mapping out "given this scenario, x, y and z happen".