refactor(tests): Move remaining tests to posix 64.
* Update docs and fix up a few lingering tests to consistently use native_posix_64 target.
This commit is contained in:
parent
37f4f9eb4a
commit
64dadfb336
10 changed files with 6 additions and 6 deletions
|
@ -21,18 +21,18 @@ apt install -y gcc-multilib
|
||||||
## Building
|
## Building
|
||||||
|
|
||||||
To do this, you can build ZMK targeting the
|
To do this, you can build ZMK targeting the
|
||||||
`native_posix` board.
|
`native_posix_64` board.
|
||||||
|
|
||||||
```
|
```
|
||||||
west build --pristine --board native_posix
|
west build --pristine --board native_posix_64 -- -DZMK_CONFIG=tests/none/normal/
|
||||||
```
|
```
|
||||||
|
|
||||||
Once built, you can run the firmware locally:
|
Once built, you can run the firmware locally:
|
||||||
|
|
||||||
```
|
```
|
||||||
./build/zephyr/zephyr.exe
|
./build/zephyr/zmk.exe
|
||||||
```
|
```
|
||||||
|
|
||||||
## Virtual Key Events
|
## Virtual Key Events
|
||||||
|
|
||||||
The virtual key presses are hardcoded in `boards/native_posix.overlay` file, should you want to change the sequence to test various actions like Mod-Tap, etc.
|
The virtual key presses are hardcoded in `boards/native_posix_64.overlay` file, should you want to change the sequence to test various actions like Mod-Tap, etc.
|
||||||
|
|
|
@ -4,7 +4,7 @@ sidebar_label: Tests
|
||||||
---
|
---
|
||||||
|
|
||||||
- Running tests requires [native posix support](posix-board.md).
|
- Running tests requires [native posix support](posix-board.md).
|
||||||
- Any folder under `/app/tests` containing `native_posix.keymap` will be selected when running `west test`.
|
- Any folder under `/app/tests` containing `native_posix_64.keymap` will be selected when running `west test`.
|
||||||
- Run tests from within the `/zmk/app` directory.
|
- Run tests from within the `/zmk/app` directory.
|
||||||
- Run a single test with `west test <testname>`, like `west test tests/toggle-layer/normal`.
|
- Run a single test with `west test <testname>`, like `west test tests/toggle-layer/normal`.
|
||||||
|
|
||||||
|
@ -13,7 +13,7 @@ sidebar_label: Tests
|
||||||
1. Copy the test set that most closely resembles the tests you will be creating.
|
1. Copy the test set that most closely resembles the tests you will be creating.
|
||||||
2. Rename the newly created test set to the behavior you're testing e.g, toggle-layer
|
2. Rename the newly created test set to the behavior you're testing e.g, toggle-layer
|
||||||
3. Modify `behavior_keymap.dtsi` to create a keymap using the behavior and related behaviors
|
3. Modify `behavior_keymap.dtsi` to create a keymap using the behavior and related behaviors
|
||||||
4. Modify `test_case/native_posix.keymap` for a simulated use case
|
4. Modify `test_case/native_posix_64.keymap` for a simulated use case
|
||||||
5. Modify `test_case/events.patterns` to collect relevant logs to the test
|
5. Modify `test_case/events.patterns` to collect relevant logs to the test
|
||||||
- See: [sed manual](https://www.gnu.org/software/sed/manual/sed.html) and
|
- See: [sed manual](https://www.gnu.org/software/sed/manual/sed.html) and
|
||||||
[tutorial](https://www.digitalocean.com/community/tutorials/the-basics-of-using-the-sed-stream-editor-to-manipulate-text-in-linux)
|
[tutorial](https://www.digitalocean.com/community/tutorials/the-basics-of-using-the-sed-stream-editor-to-manipulate-text-in-linux)
|
||||||
|
|
Loading…
Reference in a new issue