Currently, when a test operation fails, a JsonPatchApplicationException is thrown. This makes it hard to distinguish an input error (e.g. referencing a nonexisting path) from a failed test (it is possible by parsing the message, but a separation by exception types would be easier). The new exception type could be a subtype of JsonPatchApplicationException.
Story:
AS a developer
WHEN a test operation fails
THEN I want to receive a dedicated exception signaling that the test path has not the excpected value so I can distinguish between a syntactical error (like a wrong path) and a failed expectation.