Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Testing: split input test #2762

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from
Draft

Testing: split input test #2762

wants to merge 5 commits into from
+322 −22

Conversation

petejohanson
Copy link
Contributor

@petejohanson petejohanson commented Jan 12, 2025 •
edited
Loading

PR check-list

  • Branch has a clean commit history
  • Additional tests are included, if changing behaviors/core code that is testable.
  • Proper Copyright + License headers added to applicable files (Generally, we stick to "The ZMK Contributors" for copyrights to help avoid churn when files get edited)
  • Pre-commit used to check formatting of files, commit messages, etc.
  • Includes any necessary documentation changes.

@petejohanson petejohanson added enhancement New feature or request split tests labels Jan 12, 2025
@petejohanson petejohanson self-assigned this Jan 12, 2025
@petejohanson petejohanson force-pushed the testing/split-input-test branch from 5ffab0c to e5081b5 Compare January 12, 2025 22:19
@petejohanson
test(pointing): Add mock input device.
e2f8891 
New mock input device to generate input events for tests.
@petejohanson
test(split): Add peripheral input test.
47c3f68 
Test event propagation from peripheral input devices.
@petejohanson
fix(split): Proper scoping for local within switch.
2227d19 
Minor compile fix.
@petejohanson
chore: Fix up test snapshots after logging changes.
11b2c9e 
Adjust the test snapshots after logging changes to the central.
@petejohanson petejohanson force-pushed the testing/split-input-test branch from 7ca9957 to 11b2c9e Compare January 13, 2025 17:02
@petejohanson
fix(kscan): Don't fire last mock event twice.
40f5aa0 
Fix a bug where the kscan mock would raise the last mock event
twice before haltning processing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@petejohanson petejohanson

Labels
enhancement New feature or request split tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@petejohanson