You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
trezor-firmware/tests
Adrian Nagy 384275ac73
core/tezos: support the new protocol update (005-BABYLON)
5 years ago
..
burn_tests tests: move burn tests to root 5 years ago
click_tests tests: improve layout_lines API 5 years ago
device_tests core/tezos: support the new protocol update (005-BABYLON) 5 years ago
emulators tests/upgrade tests: patch emulators on NixOS 5 years ago
fido_tests ci: add fido2 tests to ci 5 years ago
txcache tests: move device tests to top-level 5 years ago
upgrade_tests tests: improve Shamir persistence test 5 years ago
README.md docs: improve tests documentation 5 years ago
REGISTERED_MARKERS tests: add multisig marker 5 years ago
__init__.py tests: start moving common functions to top level 5 years ago
buttons.py tests: fix grid34 5 years ago
common.py debug: Add left and right swipe direction to DebugLinkDecision message and unify terminology around swipe direction. 5 years ago
conftest.py tests: rename background.py to device_handler.py 5 years ago
device_handler.py core: improve emulator wrapper 5 years ago
download_emulators.sh tests/upgrade tests: patch emulators on NixOS 5 years ago
emulators.py core: improve emulator wrapper 5 years ago
trezor.sdcard.gz core: improve emulator wrapper 5 years ago
tx_cache.py tests: start moving common functions to top level 5 years ago

README.md

Tests

Burn tests

These tests are doing a simple read/write operations on the device to see if the hardware can endure high number of flash writes. Meant to be run on the device directly for a long period of time.

Device tests

Device tests are integration tests that can be run against either emulator or on an actual device. The Debug mode is required. These tests can be run against both Model One and Model T.

See the README for instructions how to run it.

Fido tests

Implement U2F/FIDO2 tests.

Upgrade tests

These tests test upgrade from one firmware version to another. They initialize an emulator on some specific version and then pass its storage to another version to see if the firmware operates as expected. They use fixtures from https://firmware.corp.sldev.cz/upgrade_tests/ which can be downloaded using the download_emulators.sh script.

See the README for instructions how to run it.