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
Andrew Kozlik 1ca1d77bf7
tests/sign_tx: Add a test to ensure that if the change output is modified after the user confirms the transaction, then signing fails.
5 years ago
..
burn_tests
device_tests tests/sign_tx: Add a test to ensure that if the change output is modified after the user confirms the transaction, then signing fails. 5 years ago
emulators
fido_tests/u2f-tests-hid tests: update u2ftest to auto-confirm when needed 5 years ago
txcache
upgrade_tests docs: improve tests documentation 5 years ago
README.md docs: improve tests documentation 5 years ago
REGISTERED_MARKERS
__init__.py
common.py debug: Add left and right swipe direction to DebugLinkDecision message and unify terminology around swipe direction. 5 years ago
conftest.py tests: cleanup conftest.py 5 years ago
download_emulators.sh docs: improve tests documentation 5 years ago
emulators.py tests: increase timeout for emulators to 30s 5 years ago
tx_cache.py

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.