Don't pass the event object to the handler function, but return a value instead and let the keyboardUtil do the job, since it knows the event object.
Trying to make the test more readable.
Some text ...
Added roadmap.
Update ROADMAP.md
MIT licensed
Fix year in license and changelogged.
Copy the content and style of TDDbin.com.
Rename to better reflect the use case.
Don't spy on keyboardUtil methods globally.
Show the shortcut overlay.
Split out function to be able to use it separately.
Fire a registered callback when a shortcut started.
Call the onPossibleShortcut callback for every key that is pressed, that is a possible shortcut.
Fire onShortcutEnd() callback properly.
Better group tests.
Add another edge test case.
Use util where possible, less duplication.
Fire shortcutEnd when the current shortcut turns out not to be a valid shortcut.
Fire onShortcutEnd() on keyUp of unfinished shortcut.