-
Type: Bug
-
Resolution: Fixed
-
Priority: Unknown
-
Affects Version/s: None
-
Component/s: None
What problem are you facing?
The `match` functionality, used when asserting that received documents match the expected documents in a unified test, is incorrect. There are two already identified issues (perhaps more):
- the `match` function doesn't assert for exact matches on nested documents correctly. We currently check for exact matches if we are more than 2 levels deep in an object, but the spec calls for exact matching on anything that isn't the root document.
- our command event matching is currently relying on the match function to assert correctness. fixing the above will cause the command assertions to work incorrectly, because documents that were previously not strictly compared will be strictly compared.
Acceptance Criteria
- Fix the unified runner so that our matching logic is correct.
- Refactor command event matching to match according to spec.
- Ensure that all tests pass.