Add tests for macOS key press simulation #13
Merged
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.
@ChrisC Here's a prototype of the system we discussed last week. I'm submitting it as a draft because there are three tests which don't work the way I expected them to work, and I'd like to try to understand why.
I documented them by including "(suspect behavior)" in their title and by skipping corresponding tests labeled "(intuitive behavior)". The "skipped test" approach surfaces my expectation in the tests' source code and in the output from executing them, which could be helpful if my hunch is correct and some of these behaviors are unavoidable.
We can't use this approach to observe press/release of the "Fn" key, but my initial testing suggested that we can't simulate pressing that key in the first place. This test suite will be especially reassuring if/when the code has to make the kinds of substitutions exemplified there (e.g. simulating "End" instead of "Fn + Right Arrow").
Resolves gh-12.