summaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)Author
2022-08-14Fix Caps Word to treat mod-taps more consistently. (#17463)Pascal Getreuer
* Fix Caps Word to treat mod-taps more consistently. Previously, holding any mod-tap key while Caps Word is active stops Caps Word, and this happens regardless of `caps_word_press_user()`. Yet for regular mod keys, AltGr (KC_RALT) is ignored, Shift keys are passed to `caps_word_press_user()` to determine whether to continue, and similarly, a key `RSFT(KC_RALT)` representing Right Shift + Alt is passed to `caps_word_press_user()` to determine whether to continue. This commit makes held mod-tap keys consistent with regular mod keys: * Holding a `RALT_T` mod-tap is ignored. * When holding a shift mod-tap key, `KC_LSFT` or `KC_RSFT` is passed to `caps_word_press_user()` to determine whether to continue. * When holding a Right Shift + Alt (`RSA_T`) mod-tap, `RSFT(KC_RALT)` is passed to `caps_word_press_user()`. Particularly, with this fix a user may choose to continue Caps Word when a shift mod-tap key is held by adding `KC_LSFT` and `KC_RSFT` cases in `caps_word_press_user()`. For instance as ``` bool caps_word_press_user(uint16_t keycode) { switch (keycode) { // Keycodes that continue Caps Word, with shift applied. case KC_A ... KC_Z: case KC_MINS: add_weak_mods(MOD_BIT(KC_LSFT)); // Apply shift to the next key. return true; // Keycodes that continue Caps Word, without shifting. case KC_1 ... KC_0: case KC_BSPC: case KC_DEL: case KC_UNDS: case KC_LSFT: // <<< Added here. case KC_RSFT: return true; default: return false; // Deactivate Caps Word. } } ``` * Fix Caps Word to treat mod-taps more consistently. Previously, holding any mod-tap key while Caps Word is active stops Caps Word, and this happens regardless of `caps_word_press_user()`. Yet for regular mod keys, AltGr (KC_RALT) is ignored, Shift keys are passed to `caps_word_press_user()` to determine whether to continue, and similarly, a key `RSFT(KC_RALT)` representing Right Shift + Alt is passed to `caps_word_press_user()` to determine whether to continue. This commit makes held mod-tap keys consistent with regular mod keys: * Holding a `RALT_T` mod-tap is ignored. * When holding a shift mod-tap key, `KC_LSFT` or `KC_RSFT` is passed to `caps_word_press_user()` to determine whether to continue. * When holding a Right Shift + Alt (`RSA_T`) mod-tap, `RSFT(KC_RALT)` is passed to `caps_word_press_user()`. Particularly, with this fix a user may choose to continue Caps Word when a shift mod-tap key is held by adding `KC_LSFT` and `KC_RSFT` cases in `caps_word_press_user()`. For instance as ``` bool caps_word_press_user(uint16_t keycode) { switch (keycode) { // Keycodes that continue Caps Word, with shift applied. case KC_A ... KC_Z: case KC_MINS: add_weak_mods(MOD_BIT(KC_LSFT)); // Apply shift to the next key. return true; // Keycodes that continue Caps Word, without shifting. case KC_1 ... KC_0: case KC_BSPC: case KC_DEL: case KC_UNDS: case KC_LSFT: // <<< Added here. case KC_RSFT: return true; default: return false; // Deactivate Caps Word. } } ``` * Update quantum/process_keycode/process_caps_word.c Co-authored-by: Joel Challis <git@zvecr.com>
2022-08-13Fix Caps Word capitalization when used with Combos + Auto Shift. (#17549)Pascal Getreuer
2022-08-06[Core] Process all changed keys in one scan loop, deprecate ↵Stefan Kerkmann
`QMK_KEYS_PER_SCAN` (#15292)
2022-06-16tap-dance: Rename tests so that tap_dance is used consistently (#17396)Jouke Witteveen
2022-06-13tap-dance: Restructure code and document in more detail (#16394)Jouke Witteveen
2022-06-05Apply EXPECT_REPORT and EXPECT_EMPTY_REPORT (#17311)Stefan Kerkmann
...convenience macros to test cases that where missed during #17284
2022-06-05Fix and add unit tests for Caps Word to work with Unicode Map, Auto Shift, ↵Pascal Getreuer
Retro Shift. (#17284) * Fix Caps Word and Unicode Map * Tests for Caps Word + Auto Shift and Unicode Map. * Fix formatting * Add additional keyboard report expectation macros This commit defines five test utilities, EXPECT_REPORT, EXPECT_UNICODE, EXPECT_EMPTY_REPORT, EXPECT_ANY_REPORT and EXPECT_NO_REPORT for use with TestDriver. EXPECT_REPORT sets a gmock expectation that a given keyboard report will be sent. For instance, EXPECT_REPORT(driver, (KC_LSFT, KC_A)); is shorthand for EXPECT_CALL(driver, send_keyboard_mock(KeyboardReport(KC_LSFT, KC_A))); EXPECT_UNICODE sets a gmock expectation that a given Unicode code point will be sent using UC_LNX input mode. For instance for U+2013, EXPECT_UNICODE(driver, 0x2013); expects the sequence of keys: "Ctrl+Shift+U, 2, 0, 1, 3, space". EXPECT_EMPTY_REPORT sets a gmock expectation that a given keyboard report will be sent. For instance EXPECT_EMPTY_REPORT(driver); expects a single report without keypresses or modifiers. EXPECT_ANY_REPORT sets a gmock expectation that a arbitrary keyboard report will be sent, without matching its contents. For instance EXPECT_ANY_REPORT(driver).Times(1); expects a single arbitrary keyboard report will be sent. EXPECT_NO_REPORT sets a gmock expectation that no keyboard report will be sent at all. * Add tap_key() and tap_keys() to TestFixture. This commit adds a `tap_key(key)` method to TestFixture that taps a given KeymapKey, optionally with a specified delay between press and release. Similarly, the method `tap_keys(key_a, key_b, key_c)` taps a sequence of KeymapKeys. * Use EXPECT_REPORT, tap_keys, etc. in most tests. This commit uses EXPECT_REPORT, EXPECT_UNICODE, EXPECT_EMPTY_REPORT, EXPECT_NO_REPORT, tap_key() and tap_keys() test utilities from the previous two commits in most tests. Particularly the EXPECT_REPORT macro is frequently useful and makes a nice reduction in boilerplate needed to express many tests. Co-authored-by: David Kosorin <david@kosorin.net>
2022-05-20Continue Caps Word when AltGr (right Alt) is held. (#17156)Pascal Getreuer
This is a minor bug fix for Caps Word. Currently, Caps Word turns off whenever a non-shift mod becomes active. This is done to avoid interfering with hotkeys. This commit makes an exception to continue Caps Word when AltGr (right Alt) is held. Outside the US, the AltGr key is used to type additional symbols (https://en.wikipedia.org/wiki/AltGr_key). Depending on the language, these may include symbols used within words like accented letters where it would be desirable to continue Caps Word.
2022-05-14Format code according to conventions (#17096)QMK Bot
2022-05-14Enhancement and fixes of "Secure" feature (#16958)Drashna Jaelre
2022-05-14[Core] Add Caps Word feature to core (#16588)Pascal Getreuer
Co-authored-by: precondition <57645186+precondition@users.noreply.github.com> Co-authored-by: Drashna Jaelre <drashna@live.com>
2022-02-12Format code according to conventions (#16322)QMK Bot
2022-01-24Rip out old macro and action_function system (#16025)Ryan
* Rip out old macro and action_function system * Update quantum/action_util.c Co-authored-by: Joel Challis <git@zvecr.com>
2021-12-14[Core] Don't send keyboard reports that propagate no changes to the host ↵Stefan Kerkmann
(#14065)
2021-11-23 [Tests] Increase QMK test coverage take 2 (#15269)Stefan Kerkmann
* Add per-test keymaps * Add better trace and info logs for failed unit-tests * Add layer state assertion with tracing message * Use individual test binaries configuration options * Add basic qmk functionality tests * Add tap hold configurations tests * Add auto shift tests Co-authored-by: Nick Brassel <nick@tzarc.org>
2021-11-23Revert "[Tests] Increase QMK test coverage (#13789)"Nick Brassel
This reverts commit b6054c0206609f3755f71d819643644d250288b0.
2021-11-23[Tests] Increase QMK test coverage (#13789)Stefan Kerkmann
* Add per-test keymaps * Add better trace and info logs for failed unit-tests * Add layer state assertion with tracing message * Use individual test binaries configuration options * Add basic qmk functionality tests * Add tap hold configurations tests * Add auto shift tests * `qmk format-c * Fix tests Co-authored-by: Nick Brassel <nick@tzarc.org>
2021-11-03Basic keycode overhaul (#14726)Ryan
2021-09-29[Core] Fix "6kro enable" and clarify naming (#14563)Drashna Jaelre
* Fix USB_6KRO_ENABLE compilation errors * Add info to docs * Rename define to be more accurate * Remove unused rule * Refixe docs
2021-07-25Allow output of logging when running unit tests (#13556)Joel Challis
* Initial pass at enabling logging for unit tests * Add to docs * Bind debug for more test types * Force everything * Tidy up slightly
2020-12-30Missed a couple more `#pragma once`s (#11351)Ryan
2020-12-28Ensure single newline at EOF for core files (#11310)Ryan
2020-03-13format code according to conventions [skip ci]QMK Bot
2020-03-13Fix pressing two keys with the same keycode but different modifiers (#2710)fredizzimo
* Fix extra keyboard report during test_fixture teardown * Add tests for pressing two keys with only different modifers * Fix #1708 When two keys that use the same keycode, but different modifiers were pressed at the same time, the second keypress wasn't registered. This is fixed by forcing a key release when we detect a new press for the same keycode. * Fix the NKRO version of is_key_pressed * Fix uninitalized loop variable Co-authored-by: Jack Humbert <jack.humb@gmail.com>
2019-08-30clang-format changesskullY
2019-01-11Remove empty action_function()fauxpark
2017-12-15add tests for action_layer.c and reset layer state after testsColin T.A. Gray
2017-07-11Fix unreferenced errors with mingw compiler and unit testsFred Sundvik
2017-07-08Reference issue #1478 from the unit testsFred Sundvik
2017-07-08Reference issue #1477 from the unit testsFred Sundvik
2017-07-08Reference issue #524 from the unit testsFred Sundvik
2017-07-08Reference issue #1476 from the unit testsFred Sundvik
2017-07-08Configure vscode file associations, use hpp instead of hFred Sundvik
2017-07-08Fix keymap formattingFred Sundvik
2017-07-08Add tests for macrosFred Sundvik
2017-07-08Rename tests to start with test_Fred Sundvik
2017-07-08Add basic timing support, and SFT_T testsFred Sundvik
Also expose some bugs...
2017-07-08Add test for a combo keyFred Sundvik
2017-07-08Add simple modifier testFred Sundvik
2017-07-08Improve the tests a bitFred Sundvik
2017-07-08A bigger test matrix, and test for unmapped keysFred Sundvik
2017-07-08Rename test.cpp to keypress.cppFred Sundvik
2017-07-08Move test keymap to keymap.cFred Sundvik
2017-06-19Add a couple of todos to keyboard_report_util.cppFred Sundvik
Also print the modifier state
2017-06-19More natural interface for setting keyboard ledsFred Sundvik
2017-06-18Add a test fixtureFred Sundvik
It only initializes QMK once, and clears the matrix after each test.
2017-06-18Test two keys pressed at onceFred Sundvik
2017-06-18Actually test for correct key pressesFred Sundvik
2017-06-18Fix the order of init and driver creationFred Sundvik
2017-06-18Add a couple of basic tests and implement driver mockFred Sundvik