SAW Python missing counterexamples #1551
Labels
better-when-documented
Issues whose root causes include missing or wrong documentation
documentation
Issues involving documentation
subsystem: saw-remote-api
Issues related to the SAW server and its RPC bindings
topics: error-handling
Issues involving the way SAW responds to an error condition
type: enhancement
Issues describing an improvement to an existing feature or capability
Milestone
SAW can usually produce counterexamples (and additional details) when verification fails. However, these are not displayed to the user when using SAW through the Python interface.
It would be ideal if using the remote interfaces produced the same level of detail as SAWScript itself.
As an example, consider the following function: https://github.com/signalapp/libsignal-protocol-c/blob/3a83a4f4ed2302ff6e68ab569c88793b50c22d28/src/signal_protocol.c#L605-L611
The following specification (in Python) contains an off-by-one error in the postconditions
The resulting error is below. It does not really tell you what went wrong.
A similar spec in SAWScript (with the same error) is below:
This produces a better error message that includes a counter example:
The text was updated successfully, but these errors were encountered: