qmk_firmware.git - Keyboard layout for Planck

Age	Commit message (Collapse)	Author
2023-10-23	Separate 6KRO and NKRO report structs (#22267)	Ryan

2023-08-27	Unicode, Unicodemap and UCIS refactor (#21659)	Ryan

2022-10-06	Refactor `send_extra` (#18615)	Ryan

2022-09-02	Simplify extrakeys sending at the host driver level (#18230)	Ryan
	* Simplify extrakeys sending at the host driver level * There are two arguments here * Wrong syntax * Adjust keyboards which use a custom host driver
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>
2022-02-12	Format code according to conventions (#16322)	QMK Bot

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>
2019-08-30	clang-format changes	skullY

2017-07-08	Configure vscode file associations, use hpp instead of h	Fred Sundvik

2017-06-19	More natural interface for setting keyboard leds	Fred Sundvik

2017-06-18	Actually test for correct key presses	Fred Sundvik

2017-06-18	Add a couple of basic tests and implement driver mock	Fred Sundvik