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
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.
The text was updated successfully, but these errors were encountered:
I have taken a look at all depentent repositories (github.com) with 100+ stars (and activity in the last 5 years). None of them should be affected when we create a new exception that inherits from JsonPatchApplicationException.
Currently, when a
test
operation fails, aJsonPatchApplicationException
is thrown. This makes it hard to distinguish an input error (e.g. referencing a nonexistingpath
) 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 ofJsonPatchApplicationException
.Story:
AS a developer
WHEN a
test
operation failsTHEN 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.The text was updated successfully, but these errors were encountered: