summaryrefslogtreecommitdiffstats
path: root/tests/test_common
Commit message (Collapse)AuthorAgeFilesLines
* Refactor `send_extra` (#18615)Ryan2022-10-062-4/+4
|
* Simplify extrakeys sending at the host driver level (#18230)Ryan2022-09-022-11/+5
| | | | | | | | | * Simplify extrakeys sending at the host driver level * There are two arguments here * Wrong syntax * Adjust keyboards which use a custom host driver
* Fix Caps Word capitalization when used with Combos + Auto Shift. (#17549)Pascal Getreuer2022-08-132-0/+23
|
* Fix and add unit tests for Caps Word to work with Unicode Map, Auto Shift, ↵Pascal Getreuer2022-06-054-3/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Format code according to conventions (#16322)QMK Bot2022-02-125-16/+46
|
* [Core] Don't send keyboard reports that propagate no changes to the host ↵Stefan Kerkmann2021-12-141-3/+0
| | | | (#14065)
* [Tests] Increase QMK test coverage take 2 (#15269)Stefan Kerkmann2021-11-2312-39/+382
| | | | | | | | | | | | | | | | | * 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 Brassel2021-11-2312-382/+39
| | | | This reverts commit b6054c0206609f3755f71d819643644d250288b0.
* [Tests] Increase QMK test coverage (#13789)Stefan Kerkmann2021-11-2312-39/+382
| | | | | | | | | | | | | | | | | | | | | * 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>
* [Core] Fix "6kro enable" and clarify naming (#14563)Drashna Jaelre2021-09-291-1/+1
| | | | | | | | | | | * Fix USB_6KRO_ENABLE compilation errors * Add info to docs * Rename define to be more accurate * Remove unused rule * Refixe docs
* Allow output of logging when running unit tests (#13556)Joel Challis2021-07-252-2/+38
| | | | | | | | | | | * Initial pass at enabling logging for unit tests * Add to docs * Bind debug for more test types * Force everything * Tidy up slightly
* Missed a couple more `#pragma once`s (#11351)Ryan2020-12-301-4/+1
|
* Ensure single newline at EOF for core files (#11310)Ryan2020-12-284-10/+6
|
* Fix pressing two keys with the same keycode but different modifiers (#2710)fredizzimo2020-03-131-3/+4
| | | | | | | | | | | | | | | | | | * 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 changesskullY2019-08-304-95/+48
|
* add tests for action_layer.c and reset layer state after testsColin T.A. Gray2017-12-152-3/+10
|
* Fix unreferenced errors with mingw compiler and unit testsFred Sundvik2017-07-113-3/+6
|
* Configure vscode file associations, use hpp instead of hFred Sundvik2017-07-087-8/+8
|
* Add basic timing support, and SFT_T testsFred Sundvik2017-07-083-4/+45
| | | | Also expose some bugs...
* Add simple modifier testFred Sundvik2017-07-081-4/+10
|
* Add a couple of todos to keyboard_report_util.cppFred Sundvik2017-06-191-0/+3
| | | | Also print the modifier state
* More natural interface for setting keyboard ledsFred Sundvik2017-06-193-5/+4
|
* Add a test fixtureFred Sundvik2017-06-184-1/+72
| | | | It only initializes QMK once, and clears the matrix after each test.
* Test two keys pressed at onceFred Sundvik2017-06-182-2/+30
|
* Actually test for correct key pressesFred Sundvik2017-06-184-5/+92
|
* Add a couple of basic tests and implement driver mockFred Sundvik2017-06-184-1/+146
|
* Dummy test matrix implementationFred Sundvik2017-06-181-0/+43