mirror of
https://github.com/keymanapp/keyman.git
synced 2026-09-10 17:47:42 +00:00
Per the spec, the `id` attribute is required for touch layers, and `modifiers` attribute is required for hardware layers. There is ambiguity in the spec at present as to whether they should be allowed for the alternative type. * Validate that the attributes are present where required. * Tighten validation of `modifiers` attribute - it cannot be empty or missing for hardware; "" != "none". * Hint if the attribute is present when it probably shouldn't be (to be potentially raised to warning or error after spec clarified). * Fixup all keyboard3 xml files to conform to spec and eliminate hints. * Add unit tests. * Removed threshold warning for coverage as kmc-ldml is already > 90%. Fixes: #12423 |
||
|---|---|---|
| .. | ||
| invalid-keyboards | ||
| keyboards | ||
| context_normalization.tests.cpp | ||
| core_ldml_min.tests.cpp | ||
| kmx_plus.tests.cpp | ||
| ldml.cpp | ||
| ldml_test_source.cpp | ||
| ldml_test_source.hpp | ||
| ldml_test_utils.cpp | ||
| ldml_test_utils.hpp | ||
| meson.build | ||
| README.md | ||
| transforms.tests.cpp | ||
| unicode.tests.cpp | ||
| write_node_versions.js | ||
LDML unit tests
This directory contains unit tests that test the LDML keyboard processing.
The driver (ldml.cpp) loads and executes the tests. Each test consist of a
Keyman keyboard source file (*.xml) and the compiled KMXPlus keyboard.
The source file contains rules and defines the setup, input and expected results.
Defining tests in the .xml file
Somewhere near the top of the file, an XML comment contains lines that define the setup, input and expected results.
Setup
- description: this is just for commenting what we test here
@@description: Tests Caps Lock env set
- capsLock: allows to set the caps lock state. The example below turns
caps-lock on at the start of the test.
[K_CAPS]in the keys comment allows toggling of caps lock.
@@capsLock: 1
- context: allows to setup a string which serves as context
@@context:
Input
- keys: defines one or more virtual keys that will be processed one after the other
@@keys: [K_1][K_CAPS][K_2][SHIFT K_3][K_4][K_CAPS][K_5][K_CAPS][K_6]
Expected Result
- expected: the resulting string of processing the input keys. In the example
below each key press is expected to output the string
'pass.'.
@@expected: pass.pass.pass.pass.pass.pass.
Running the tests
All tests can be run at once with ./build.sh --debug tests.
Alternatively it's possible to run a single test with:
cd core
build/arch/debug/tests/unit/ldml/ldml 'tests/unit/ldml/000_test_zero.xml' 'tests/unit/ldml/000_test_zero.kmx'