qmk_firmware

Commit Graph

Author	SHA1	Message	Date
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>	1 year ago
QMK Bot	63646e8906	Format code according to conventions (#16322 )	2 years ago
Stefan Kerkmann	8b865a9d64	[Core] Don't send keyboard reports that propagate no changes to the host (#14065 )	2 years ago
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>	2 years ago
Nick Brassel	7746aefe94	Revert "[Tests] Increase QMK test coverage (#13789 )" This reverts commit `b6054c0206`.	2 years ago
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>	2 years ago
Drashna Jaelre	02ab7b1888	[Core] Fix "6kro enable" and clarify naming (#14563 ) * Fix USB_6KRO_ENABLE compilation errors * Add info to docs * Rename define to be more accurate * Remove unused rule * Refixe docs	2 years ago
Joel Challis	fc9fb2c775	Allow output of logging when running unit tests (#13556 ) * Initial pass at enabling logging for unit tests * Add to docs * Bind debug for more test types * Force everything * Tidy up slightly	2 years ago
Ryan	7071900407	Missed a couple more `#pragma once`s (#11351 )	3 years ago
Ryan	1b7b72c0e9	Ensure single newline at EOF for core files (#11310 )	3 years ago
fredizzimo	9e8767917d	Fix pressing two keys with the same keycode but different modifiers (#2710 ) * 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>	4 years ago
skullY	b624f32f94	clang-format changes	4 years ago
Colin T.A. Gray	4ea3bbdb4c	add tests for action_layer.c and reset layer state after tests	6 years ago
Fred Sundvik	78545b9509	Fix unreferenced errors with mingw compiler and unit tests	6 years ago
Fred Sundvik	67f722c9c8	Configure vscode file associations, use hpp instead of h	6 years ago
Fred Sundvik	4e69a8bda6	Add basic timing support, and SFT_T tests Also expose some bugs...	6 years ago
Fred Sundvik	cae7a9c3ec	Add simple modifier test	6 years ago
Fred Sundvik	fb9b8dadb9	Add a couple of todos to keyboard_report_util.cpp Also print the modifier state	7 years ago
Fred Sundvik	43d8fa5bf1	More natural interface for setting keyboard leds	7 years ago
Fred Sundvik	36f820be7e	Add a test fixture It only initializes QMK once, and clears the matrix after each test.	7 years ago
Fred Sundvik	e85b185796	Test two keys pressed at once	7 years ago
Fred Sundvik	bd1729d5be	Actually test for correct key presses	7 years ago
Fred Sundvik	3bb0586acc	Add a couple of basic tests and implement driver mock	7 years ago
Fred Sundvik	a72e8f0865	Dummy test matrix implementation	7 years ago

24 Commits (25033d5d9ee1298c719d8e33a96eb7cabb9c04ac)