Author	SHA1	Message	Date
precondition	1abf8f3e8b	[Feature] Send a dummy keycode to neutralize flashing modifiers in retro tap and key overrides (#20992)	2023-07-08 00:18:02 +10:00
Stefan Kerkmann	c2b13bd77b	Introduce VERIFY_AND_CLEAR shorthand (#19370) ... Which is just a syntactic sugar for testing::Mock::VerifyAndClearExpectations to reduce the visual clutter in unit-tests.	2022-12-18 21:55:14 +01:00
Joel Challis	456d6f3342	Remove legacy keycodes from unit tests (#18430)	2022-09-20 08:52:43 +02:00
Stefan Kerkmann	4c48760558	Apply EXPECT_REPORT and EXPECT_EMPTY_REPORT (#17311) ... ...convenience macros to test cases that where missed during #17284	2022-06-05 20:06:05 +01:00
Pascal Getreuer	95d20e6d8b	Fix and add unit tests for Caps Word to work with Unicode Map, Auto Shift, 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-06-05 09:14:02 +02:00
Stefan Kerkmann	a24bdccee0	[Tests] Increase QMK test coverage take 2 (#15269) ... * 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 13:31:01 +11:00
Nick Brassel	7746aefe94	Revert "[Tests] Increase QMK test coverage (#13789)" ... This reverts commit b6054c0206.	2021-11-23 09:54:04 +11:00
Stefan Kerkmann	b6054c0206	[Tests] Increase QMK test coverage (#13789) ... * 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-23 08:15:04 +11:00