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
But in our case, the order of the results isn't important, just the array entries. If possible, it'd be great to add another key to the meta file to flag whether the test should be run in an order-agnostic-test-comparison or not.
Not sure on the flow for approvals here, but I'm happy to do the PR for these changes, but wanting to get people's thoughts on it before doing so. Please let me know, thank you!
The use case here is around an issue facing issues where our migrations that use external APIs as part of the migration, aren't always completed in the order that they start in.
That's why a less strict check on the expected results vs outcome, ignoring order would be useful for us. Does that make sense?
Currently, the compareOutput() function compares arrays strictly by order.
But in our case, the order of the results isn't important, just the array entries. If possible, it'd be great to add another key to the meta file to flag whether the test should be run in an
order-agnostic-test-comparison
or not.Example where it's currently failing:
The text was updated successfully, but these errors were encountered: