diff-sequences: Double-check number of differences in tests #6953
+62
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
To increase confidence in such a complex algorithm, call a simpler baseline algorithm to compute the number of differences between sequences independently in many of the tests.
Test plan
The new criterion passes for the existing tests which use it.
By the way, it finally hit me that history of changes to files in repo might be better fuzz inputs to diff algorithm than anything I could generate. So offline, I compared number of differences from complex to simpler algorithms for 10306 files in the 2000 commits going back in history from Jest 23.5.0 Ha ha, image files were fuzzier than I wanted, so filtered to js, json, md, and snap files.