qmk_firmware

Author	SHA1	Message	Date
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	4 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>	6 years ago
skullY	b624f32f94	clang-format changes	6 years ago
Colin T.A. Gray	4ea3bbdb4c	add tests for action_layer.c and reset layer state after tests	8 years ago
Fred Sundvik	78545b9509	Fix unreferenced errors with mingw compiler and unit tests	9 years ago
Fred Sundvik	67f722c9c8	Configure vscode file associations, use hpp instead of h	9 years ago
Fred Sundvik	4e69a8bda6	Add basic timing support, and SFT_T tests Also expose some bugs...	9 years ago
Fred Sundvik	43d8fa5bf1	More natural interface for setting keyboard leds	9 years ago
Fred Sundvik	36f820be7e	Add a test fixture It only initializes QMK once, and clears the matrix after each test.	9 years ago