summaryrefslogtreecommitdiff
path: root/tests/basic
AgeCommit message (Collapse)Author
2023-05-13Add a user callback for pre process record (#20584)Albert Y
2023-04-03Fix OSMs getting stuck (#20034)Kasimir Pihlasviita
2023-02-14Fix Layer Mod handling of with right-handed mods. (#19845)Pascal Getreuer
2022-12-18Introduce 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-15[Test] Reset timer for every unit test and provide timestamps for log ↵Stefan Kerkmann
messages (#17028)
2022-11-28Bug17281 - Retain momentary layers until the end of tapping (#17282)Felix Kuehling
* Make process_tapping more readable Move most #ifdefs into conditionally defined macros to make the logic easier to follow. * Retain momentary layers until the end of tapping This allows mod-tap and layer-tap keys on layers to behave as expected. Bug: https://github.com/qmk/qmk_firmware/issues/17281 * Add tests for delayed mod/layer release while tapping Mods and layer key release is delayed while tapping is in progress to ensure that the tap is registered with the modifier state and on the layer where the key was first pressed. Signed-off-by: Felix Kuehling <felix.kuehling@gmail.com>
2022-11-12Don't clear keys on layer change unless STRICT_LAYER_RELEASE is enabled (#18577)Drashna Jaelre
* Don't clear mousekeys unless clearing keys * Revert "Don't clear mousekeys unless clearing keys" This reverts commit 29a0c06b547d72b80d416a8b6fab478c77fbd247. * Just don't clear anything on layer set * Fix lint * Enable test?
2022-08-06[Core] Process all changed keys in one scan loop, deprecate ↵Stefan Kerkmann
`QMK_KEYS_PER_SCAN` (#15292)
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-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
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-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
2017-06-18Add keymapFred Sundvik
2017-06-18Split common.mk into common.mk and common_features.mkFred Sundvik
To support including keyboard/keymap specific rules before it
2017-06-18Define MATRIX_COLS and MATRIX_ROWSFred Sundvik
2017-06-18Add basic infrastrucure for building full testsFred Sundvik