-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
diff-sequences: Double-check number of differences in tests #6953
Conversation
Codecov Report
@@ Coverage Diff @@
## master #6953 +/- ##
=======================================
Coverage 66.97% 66.97%
=======================================
Files 250 250
Lines 10379 10379
Branches 4 3 -1
=======================================
Hits 6951 6951
Misses 3427 3427
Partials 1 1 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More tests are always good 🙂
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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.