mutest: new exact_match flag for match and wait step

[liambrady]

Adds in new exact_match flag for (in)exact matching. This results in the following states:

For the match and wait steps (non-json):

• If true, then search for the provided string exactly within the command output (substring match). (new behavior)
• If false, then perform a regex search on the command output using the provided pattern.

For the match_json and wait_json steps:

• If true, then exactly match the provided and output json against each other.
• If false, then both search for and match the provided json's fields against those in the cmd output (but not vice versa). (new behavior)
  • The exact rules for matching in this case have been added to the munet documentation source files

And the new default behavior of munet is for exact matching to be set to false.

• This changes the default behavior of json matching, which previously was always an exact match

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: -0.02% ⚠️

Comparison is base (0869d8f) 60.17% compared to head (1a8b4be) 60.16%.
Report is 1 commits behind head on main.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #25      +/-   ##
==========================================
- Coverage   60.17%   60.16%   -0.02%     
==========================================
  Files          17       17              
  Lines        5153     5154       +1     
==========================================
  Hits         3101     3101              
- Misses       2052     2053       +1     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[choppsv1]

Does json_cmp always return these key-valus at the top level? i.e., what if you have a diff in a dict in a dict?

json1 = '{ "foo": { "bar": { "one": 1 } } }'
json2 = '{ "foo": { "bar": { "one": 1, "two": 2 } } }'

[liambrady]

From my testing, it always appeared that they did. The top-level key value is then associated with an array of paths locating any differences of the specified key value type.

For example, json_diff(json.loads(json1), json.loads(json2)) returns the DeepDiff object which, when converted to a dict or list at all levels, is equivalent to {'dictionary_item_added':["root['foo']['bar']['two']"]}

Similarly, json_diff(json.loads(json2), json.loads(json1)) returns the DeepDiff object which, when converted to a dict or list at all levels, is equivalent to {'dictionary_item_removed':["root['foo']['bar']['two']"]}

[choppsv1]

ok thanks