qmk_firmware - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	[Core] Process all changed keys in one scan loop, deprecate ↵	Stefan Kerkmann	2022-08-06	1	-22/+0
\| \| \| \|	`QMK_KEYS_PER_SCAN` (#15292)
*	Fix and add unit tests for Caps Word to work with Unicode Map, Auto Shift, ↵	Pascal Getreuer	2022-06-05	1	-48/+48
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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>
*	[Core] Don't send keyboard reports that propagate no changes to the host ↵	Stefan Kerkmann	2021-12-14	1	-29/+26
\| \| \| \|	(#14065)
*	[Tests] Increase QMK test coverage take 2 (#15269)	Stefan Kerkmann	2021-11-23	1	-68/+145
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* 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>
*	Revert "[Tests] Increase QMK test coverage (#13789)"	Nick Brassel	2021-11-23	1	-131/+54
\| \| \| \|	This reverts commit b6054c0206609f3755f71d819643644d250288b0.
*	[Tests] Increase QMK test coverage (#13789)	Stefan Kerkmann	2021-11-23	1	-54/+131
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* 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>
*	Basic keycode overhaul (#14726)	Ryan	2021-11-03	1	-36/+36
\|
*	format code according to conventions [skip ci]	QMK Bot	2020-03-13	1	-104/+104
\|
*	Fix pressing two keys with the same keycode but different modifiers (#2710)	fredizzimo	2020-03-13	1	-1/+117
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* 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>
*	clang-format changes	skullY	2019-08-30	1	-3/+3
\|
*	Reference issue #524 from the unit tests	Fred Sundvik	2017-07-08	1	-0/+3
\|
*	Reference issue #1476 from the unit tests	Fred Sundvik	2017-07-08	1	-0/+4
\|
*	Configure vscode file associations, use hpp instead of h	Fred Sundvik	2017-07-08	1	-1/+1
\|
*	Rename tests to start with test_	Fred Sundvik	2017-07-08	1	-0/+117