| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-07-08 | [Feature] Send a dummy keycode to neutralize flashing modifiers in retro tap ↵ | precondition | |
| and key overrides (#20992) | |||
| 2023-04-03 | Make IGNORE_MOD_TAP_INTERRUPT the default behaviour for mod-taps (#20211) | precondition | |
| 2023-02-22 | [Bug] Fix compilation error when defining QUICK_TAP_TERM_PER_KEY (#19893) | precondition | |
| 2023-01-02 | Allow mod-tap hold action on one shot layer (#19214) | David Kosorin | |
| 2022-12-18 | Introduce VERIFY_AND_CLEAR shorthand (#19370) | Stefan Kerkmann | |
| Which is just a syntactic sugar for testing::Mock::VerifyAndClearExpectations to reduce the visual clutter in unit-tests. | |||
| 2022-12-13 | Remove IGNORE_MOD_TAP_INTERRUPT_PER_KEY in favour of ↵ | precondition | |
| HOLD_ON_OTHER_KEY_PRESS_PER_KEY (#15741) | |||
| 2022-12-12 | Format code according to conventions (#19305) | QMK Bot | |
| 2022-12-12 | [Core] Replace Tapping Force Hold feature with Quick Tap Term (#17007) | Albert Y | |
| * Replace Tapping Force Hold feature with Quick Tap Term * Replace keyboard level TAPPING_FORCE_HOLD with QUICK_TAP_TERM 0 * Deprecate force hold in info_config.json * Before and after quick tap term unit tests * Quick tap unit tests iteration * Keymap config.h correction * Remove TAPPING_FORCE_HOLD_PER_KEY macros that were missed * Add two more test cases for quick tap * Replace TAPPING_FORCE_HOLD with QUICK_TAP_TERM in configs #2 * Replace TAPPING_FORCE_HOLD_PER_KEY with QUICK_TAP_TERM_PER_KEY in configs #2 * Add function declaration for get_quick_tap_term Co-authored-by: Stefan Kerkmann <karlk90@pm.me> | |||
| 2022-10-23 | Format code according to conventions (#18818) | QMK Bot | |
| 2022-10-22 | Add unit tests for HOLD_ON_OTHER_KEY_PRESS (#18721) | precondition | |
| * Add HOLD_ON_OTHER_KEY_PRESS to data/ files * Add unit tests for HOLD_ON_OTHER_KEY_PRESS | |||
| 2022-09-20 | Remove legacy keycodes from unit tests (#18430) | Joel Challis | |
| 2022-08-15 | [Bug] Add key event check to `is_tap_record` and remove `is_tap_key` (#18063) | Stefan Kerkmann | |
| 2022-06-05 | Apply EXPECT_REPORT and EXPECT_EMPTY_REPORT (#17311) | Stefan Kerkmann | |
| ...convenience macros to test cases that where missed during #17284 | |||
| 2022-06-05 | Fix 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> | |||
| 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-23 | Revert "[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> | |||
 |
index : qmk_firmware.git | |
| Keyboard layout for Planck | KJ |
| summaryrefslogtreecommitdiff |