2021-11-23 03:31:01 +01:00
|
|
|
/* Copyright 2021 Stefan Kerkmann
|
|
|
|
|
*
|
|
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
|
* the Free Software Foundation, either version 2 of the License, or
|
|
|
|
|
* (at your option) any later version.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
|
* along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
*/
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
#include "config.h"
|
2021-11-23 03:31:01 +01:00
|
|
|
#include "keyboard_report_util.hpp"
|
|
|
|
|
#include "keycode.h"
|
|
|
|
|
#include "test_common.hpp"
|
|
|
|
|
#include "action_tapping.h"
|
|
|
|
|
#include "test_fixture.hpp"
|
|
|
|
|
#include "test_keymap_key.hpp"
|
|
|
|
|
|
|
|
|
|
using testing::_;
|
|
|
|
|
using testing::InSequence;
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
class QuickTap : public TestFixture {};
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
TEST_F(QuickTap, tap_regular_key_while_mod_tap_key_is_held) {
|
2021-11-23 03:31:01 +01:00
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
2022-12-12 16:52:22 +01:00
|
|
|
auto mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
2022-12-12 17:02:15 +01:00
|
|
|
auto regular_key = KeymapKey(0, 2, 0, KC_A);
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
set_keymap({mod_tap_key, regular_key});
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press mod-tap key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Press regular key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
regular_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release regular key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
regular_key.release();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_LSFT));
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Idle for tapping term of mod tap hold key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_LSFT, KC_A));
|
|
|
|
|
EXPECT_REPORT(driver, (KC_LSFT));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
idle_for(TAPPING_TERM - 3);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
TEST_F(QuickTap, tap_mod_tap_key_while_mod_tap_key_is_held) {
|
2021-11-23 03:31:01 +01:00
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
2022-12-12 16:52:22 +01:00
|
|
|
auto first_mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
|
|
|
|
auto second_mod_tap_key = KeymapKey(0, 2, 0, RSFT_T(KC_A));
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
set_keymap({first_mod_tap_key, second_mod_tap_key});
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press first mod-tap key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
first_mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press second mod-tap key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
second_mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release second tap-hold key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
second_mod_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release first mod-tap key */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_LSFT));
|
2022-12-12 16:52:22 +01:00
|
|
|
first_mod_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Idle for tapping term of first mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_LSFT, KC_A));
|
|
|
|
|
EXPECT_REPORT(driver, (KC_LSFT));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
idle_for(TAPPING_TERM - 3);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
TEST_F(QuickTap, tap_regular_key_while_layer_tap_key_is_held) {
|
2021-11-23 03:31:01 +01:00
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
2022-12-12 16:52:22 +01:00
|
|
|
auto layer_tap_key = KeymapKey(0, 1, 0, LT(1, KC_P));
|
2022-12-12 17:02:15 +01:00
|
|
|
auto regular_key = KeymapKey(0, 2, 0, KC_A);
|
|
|
|
|
auto layer_key = KeymapKey(1, 2, 0, KC_B);
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
set_keymap({layer_tap_key, regular_key, layer_key});
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press layer-tap key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
layer_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Press regular key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
regular_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release regular key */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2021-11-23 03:31:01 +01:00
|
|
|
regular_key.release();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release layer-tap key */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_REPORT(driver, (KC_A, KC_P));
|
|
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
layer_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
TEST_F(QuickTap, tap_key_and_tap_again_before_quick_tap_term) {
|
2021-11-23 03:31:01 +01:00
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
2022-12-12 16:52:22 +01:00
|
|
|
auto mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
set_keymap({mod_tap_key});
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press mod-tap key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.release();
|
|
|
|
|
idle_for(QUICK_TAP_TERM - 10);
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press and tap mod-tap key again. */
|
|
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
mod_tap_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release mod-tap key. */
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
|
|
|
|
mod_tap_key.release();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
TEST_F(QuickTap, tap_key_and_hold_again_before_quick_tap_term) {
|
|
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
|
|
|
|
auto mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
|
|
|
|
|
|
|
|
|
set_keymap({mod_tap_key});
|
|
|
|
|
|
|
|
|
|
/* Press mod-tap key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.release();
|
|
|
|
|
idle_for(QUICK_TAP_TERM - 10);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Press and hold mod-tap key again. */
|
|
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
mod_tap_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Wait until tapping term expired */
|
|
|
|
|
EXPECT_NO_REPORT(driver);
|
|
|
|
|
idle_for(TAPPING_TERM);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release mod-tap key. */
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
|
|
|
|
mod_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
TEST_F(QuickTap, tap_key_and_tap_again_after_quick_tap_term) {
|
2021-11-23 03:31:01 +01:00
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
2022-12-12 16:52:22 +01:00
|
|
|
auto mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
set_keymap({mod_tap_key});
|
2021-11-23 03:31:01 +01:00
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press mod-tap key. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.press();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.release();
|
|
|
|
|
idle_for(QUICK_TAP_TERM + 10);
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Press mod-tap key again. */
|
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>
2022-06-05 09:14:02 +02:00
|
|
|
EXPECT_NO_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release mod-tap key. */
|
|
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
|
|
|
|
mod_tap_key.release();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
TEST_F(QuickTap, tap_key_and_hold_again_after_quick_tap_term) {
|
|
|
|
|
TestDriver driver;
|
|
|
|
|
InSequence s;
|
|
|
|
|
auto mod_tap_key = KeymapKey(0, 1, 0, SFT_T(KC_P));
|
|
|
|
|
|
|
|
|
|
set_keymap({mod_tap_key});
|
|
|
|
|
|
|
|
|
|
/* Press mod-tap key. */
|
|
|
|
|
EXPECT_NO_REPORT(driver);
|
|
|
|
|
mod_tap_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Release mod-tap key. */
|
|
|
|
|
EXPECT_REPORT(driver, (KC_P));
|
|
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
|
|
|
|
mod_tap_key.release();
|
|
|
|
|
idle_for(QUICK_TAP_TERM + 10);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Press and hold mod-tap key again. */
|
|
|
|
|
EXPECT_NO_REPORT(driver);
|
|
|
|
|
mod_tap_key.press();
|
|
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
|
|
|
|
/* Wait until tapping term expired */
|
|
|
|
|
EXPECT_REPORT(driver, (KC_LSFT));
|
2021-11-23 03:31:01 +01:00
|
|
|
idle_for(TAPPING_TERM);
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
|
2022-12-12 16:52:22 +01:00
|
|
|
/* Release mod-tap key. */
|
2022-06-05 21:06:05 +02:00
|
|
|
EXPECT_EMPTY_REPORT(driver);
|
2022-12-12 16:52:22 +01:00
|
|
|
mod_tap_key.release();
|
2021-11-23 03:31:01 +01:00
|
|
|
run_one_scan_loop();
|
|
|
|
|
testing::Mock::VerifyAndClearExpectations(&driver);
|
|
|
|
|
}
|
