JSON comparison system - Add new param to allow custom validation start point in JSON hierarchy #120
Labels
feature-request
Requesting a new product feature. Used by issue templates
triage-required
Triage required on a new issue logged for this project. Used by issue templates
Prerequisites
Feature request summary
Enabling the ability to specify a custom starting point in the
actual
side JSON hierarchy will allow test writers to make the testing intent more clear:actual
JSON does not have to be manipulatedexpected
JSON does not need wrapper containers to match the hierarchy ofactual
This supports the use case of test case validation that is only interested in a specific child node in the JSON hierarchy onwards. With the change, the user no longer has to maintain the JSON hierarchy outside of what they actually want to validate
Current behavior
For example, in the current system given
actual
your
expected
would have to be:Expected behavior
With this new proposal, it could be:
actualStartPath: "level1.level2"
+Additional implementation details or code snippets
No response
The text was updated successfully, but these errors were encountered: