summaryrefslogtreecommitdiffstats
path: root/tests/test_common/test_fixture.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Remove some use of keymap.h (#20006)Joel Challis2023-03-031-1/+0
|
* Introduce VERIFY_AND_CLEAR shorthand (#19370)Stefan Kerkmann2022-12-181-2/+2
| | | | | Which is just a syntactic sugar for testing::Mock::VerifyAndClearExpectations to reduce the visual clutter in unit-tests.
* [Test] Reset timer for every unit test and provide timestamps for log ↵Stefan Kerkmann2022-12-151-13/+16
| | | | messages (#17028)
* Fix Caps Word capitalization when used with Combos + Auto Shift. (#17549)Pascal Getreuer2022-08-131-0/+16
|
* Fix and add unit tests for Caps Word to work with Unicode Map, Auto Shift, ↵Pascal Getreuer2022-06-051-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-121-1/+3
|
* [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-231-15/+127
| | | | | | | | | | | | | | | | | * 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-231-127/+15
| | | | This reverts commit b6054c0206609f3755f71d819643644d250288b0.
* [Tests] Increase QMK test coverage (#13789)Stefan Kerkmann2021-11-231-15/+127
| | | | | | | | | | | | | | | | | | | | | * 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>
* Allow output of logging when running unit tests (#13556)Joel Challis2021-07-251-2/+6
| | | | | | | | | | | * Initial pass at enabling logging for unit tests * Add to docs * Bind debug for more test types * Force everything * Tidy up slightly
* 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-301-8/+6
|
* add tests for action_layer.c and reset layer state after testsColin T.A. Gray2017-12-151-2/+7
|
* Fix unreferenced errors with mingw compiler and unit testsFred Sundvik2017-07-111-2/+2
|
* Configure vscode file associations, use hpp instead of hFred Sundvik2017-07-081-2/+2
|
* Add basic timing support, and SFT_T testsFred Sundvik2017-07-081-4/+19
| | | | Also expose some bugs...
* More natural interface for setting keyboard ledsFred Sundvik2017-06-191-2/+0
|
* Add a test fixtureFred Sundvik2017-06-181-0/+38
It only initializes QMK once, and clears the matrix after each test.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 02:54:17 +0000