arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2025-04-05 18:06:07 +00:00
Code Issues Releases Wiki Activity

docs: hardware CI test jobs

Browse Source
This commit is contained in:
Martin Milata 2021-02-05 17:36:25 +01:00
parent 48d1a7a880
commit 6050412ed4
3 changed files with 32 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ci/hardware_tests/README.md
View File

@ -1,8 +0,0 @@
# Hardware tests
Hardware tests are device tests that run against an actual device instead of an emulator.
This works thanks to [tpmb](https://github.com/mmahut/tpmb), which is a small arduino
device capable of pushing an actual buttons on the device. Currently T1 is supported
but TT might follow.
See `ci/test.yml` "hardware legacy device test" what exactly is run.

1
ci/hardware_tests/README.md Symbolic link
View File

@ -0,0 +1 @@
../../docs/ci/jobs.md

6
ci/test-hw.yml
View File

@ -2,6 +2,12 @@ image: registry.gitlab.com/satoshilabs/trezor/trezor-firmware/trezor-firmware-en
# Hardware
# Currently it's not possible to run all regular TT tests without getting into
# a state where the micropython heap is too fragmented and allocations fail
# (often manifesting as a stuck test case). For that reason some tests are
# skipped and the rest is divided into several groups with device reboots in
# between them.
# See also: https://github.com/trezor/trezor-firmware/issues/1371
hardware core regular device test:
stage: test
only:

26
docs/ci/jobs.md
View File

@ -2,7 +2,7 @@
## Environment
### Environment
### environment
Environment job builds the `ci/Dockerfile` and pushes the built docker image
into our GitLab registry. Since modifications of this Dockerfile are very rare
@ -89,3 +89,27 @@ build? This is most likely it.**
UI tests for Core. See artifacts for a comprehensive report of UI. See [tests/ui-tests](../tests/ui-tests.html#reports)
for more info.
### hardware core regular device test
[Device tests](../tests/device-tests.md) that run against an actual physical Trezor T.
The device needs to have special bootloader, found in `core/embed/bootloader_ci`, that
makes it possible to flash firmware without confirmation on the touchscreen.
All hardware tests are run nightly on the `master` branch, as well as on push to branches
with whitelisted prefix. If you want hardware tests ran on your branch, make sure its
name starts with `hw/`.
### hardware core btconly device test
Also device tests on physical Trezor T but with Bitcoin-only firmware.
### hardware legacy regular device test
[Device tests](../tests/device-tests.md) executed on physical Trezor 1.
This works thanks to [tpmb](https://github.com/mmahut/tpmb), which is a small arduino
device capable of pushing an actual buttons on the device.
### hardware legacy btconly device test
Also device tests on physical Trezor 1 but with Bitcoin-only firmware.