-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
fix(common/models): reconnects unit tests for worker-internal submodules 🎡 #7215
Conversation
User Test ResultsTest specification and instructions User tests are not required Test Artifacts
|
it('handles heavily-punctuated English text', function() { | ||
// This test case brought to you by http://unicode.org/reports/tr29/#Word_Boundaries, Figure 1. | ||
let breaks = breakWords( | ||
`The quick ("brown") fox can't jump 32.3 feet, right?` | ||
); | ||
let words = breaks.map(span => span.text); | ||
assert.deepEqual(words, [ | ||
'The', 'quick', '(', '"', 'brown', '"', ')', 'fox', "can't", | ||
'jump', '32.3', 'feet', ',', 'right', '?' | ||
]); | ||
}); |
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.
I added this one locally while diagnosing #6900, since determining whether or not the wordbreaker might be partially at fault for the mishandling of quotation marks helped me to narrow down the search space.
Changes in this pull request will be available for download in Keyman version 16.0.58-alpha |
So, it turns out that during the big 🎡 chain in which we reorganized much of the Web-related part of the repo, there were a few sets of unit tests that never got reconnected. Heck, even I missed 'em at the time.
Ran into this while investigating the wordbreaker via unit tests - I quickly realized that they were disconnected, which led me to this. Any work on enhancing the wordbreaker needs these tests fixed first.
@keymanapp-test-bot skip