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
matejcik 2ae8e954bf
chore(tests): update UI test fixtures
3 years ago
..
burn_tests
click_tests refactor(core): no implicit spaces in render_text 4 years ago
device_tests fix(core): keep value of experimental_features cached across workflow restarts 3 years ago
emulators
fido_tests
persistence_tests
txcache test: Add device test for replacement transaction with OP_RETURN output. 4 years ago
ui_tests chore(tests): update UI test fixtures 3 years ago
upgrade_tests test: Add upgrade test with enabled wipe code for legacy. 4 years ago
.gitignore
README.md
REGISTERED_MARKERS
__init__.py
bip32.py
buttons.py
common.py refactor(core): convert parts of apps.management to layouts 4 years ago
conftest.py
device_handler.py
download_emulators.sh
emulators.py
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. You are responsible to provide either an emulator or a device with Debug mode present.

Device tests

The original version of device tests. These tests can be run against both Model One and Model T.

See device-tests.md for instructions how to run it.

UI tests

UI tests use device tests and take screenshots of every screen change and compare them against fixtures. Currently for model T only.

See ui-tests.md for more info.

Click tests

Click tests are a next-generation of the Device tests. The tests are quite similar, but they are capable of imitating user's interaction with the screen.

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 upgrade-tests.md for instructions how to run it.

Persistence tests

These tests test the Persistence mode, which is currently used in the device recovery. These tests launch the emulator themselves and they are capable of restarting or stopping it simulating user's plugging in or plugging out the device.