Closed medihack closed 2 years ago
During playing around with the already existing tests it seems that can perform single token deletion recovery
does not really test the single token deletion recovery. When you simply return false
from canRecoverWithSingleTokenDeletion
then the test still passes (yes, I did a rebuild). It seems more that it tests some re-sync or so. Maybe I can come up with a better one. I will also fix the typo in the filename if you are ok with that.
I will also fix the typo in the filename if you are ok with that.
Typo fixes are always welcome, just be wary that combining source code changes and file renaming won't confuse the version history in git.
it seems that can perform single token deletion recovery does not really test the single token deletion recovery
This is a very old test (5+ years?) it is possible that some changes along the way broke some of the test's assumptions
Alright, I will fix the typo in the filename and add the return type of canTokenTypeBeInsertedInRecovery
in separate PRs.
Is this PR ok then? I must confess that the tests are a bit "constructed", but it does test it ;-)
in separate PRs. Is this PR ok then?
Sure.
I must confess that the tests are a bit "constructed", but it does test it ;-)
It is clear enough for me. 👍
Once you remove the console.log
we can merge this PR
Super and done :-)
Fixes #1753