Matcher Chaining

[tommysitu]

With matcher chaining, one can use JSONPath to get a JSON node, and use other matcher to compare its value. For example:

{
  body: [
    {
      matcher: "jsonpath"
      value: “$.user.id"
      doMatch: {
        matcher: “exact”,
        value: “1"
    }
  ]
}

This removes the stress of composing and testing complex jsonpath/xpath expressions, which may not be supported by the current jsonpath/xpath library hoverfly is using. The matcher will be more readable too.

[kapishmalik]

@tommysitu can I take this up?

[kapishmalik]

@tommysitu I am currently working on this request.

[tommysitu]

Some work has been done here to allow one level of nesting for the form matcher: #1025 you might find it useful @kapishmalik

[kapishmalik]

@tommysitu I was thinking to change return type of all matchers from bool to string, bool...i.e. matchedvalue, ismatched or not so that I keep on iterating till doMatch is nil. Whenever the value of matcher returns false, I should return false otherwise true after iteration. Hope it makes some sense. I m changing return type so that it becomes generic and we can use doMatch with any of matchers. Matched value which we need to return depends on the matcher. It ll be returning context of that matcher that matched. For eg for jsonpathmatcher, I will be returning value of key, jsonpartialmatcher, I will be returning subset of json which matched and so on. Or other approach would be to have separate matching logic in similar way as done in above implemented approach.

Approach 1 will allow any matcher to be used with doMatch and makes it generic.

[kapishmalik]

@tommysitu I have raised two PRs(#1035 and #1036) for this with two different ways of implementation for the same above approach1. Both implements matcher chaining. IMO, PR #1036 is a better version... whichever makes more sense, we can go with that.