1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-12 17:38:13 +00:00
trezor-firmware/tests
2024-12-06 09:24:25 +01:00
..
burn_tests
click_tests test: update click tests 2024-12-06 09:24:25 +01:00
connect_tests
device_tests test: update device tests 2024-12-06 09:24:25 +01:00
emulators
fido_tests
persistence_tests refactor(python,tests): add is_invalidated flag to client, do not set the emulator.client outside from emulator 2024-12-06 09:24:25 +01:00
txcache refactor(test): use forged mainnet transactions 2024-12-02 12:21:24 +01:00
ui_tests test: update ui tests 2024-12-06 09:24:25 +01:00
upgrade_tests refactor(python,tests): add is_invalidated flag to client, do not set the emulator.client outside from emulator 2024-12-06 09:24:25 +01:00
__init__.py
.gitignore
bip32.py
buttons.py
common.py test: update test framework 2024-12-06 09:24:25 +01:00
conftest.py fix(tests): change xfail to skip when using protocol_marker 2024-12-06 09:24:25 +01:00
device_handler.py test: update test framework 2024-12-06 09:24:25 +01:00
download_emulators.sh
emulators.py
github.py fix(tests): make update_fixtures.py fetch legacy fixtures 2024-11-05 18:56:03 +01:00
gitlab.py
input_flows_helpers.py feat(core/ui): continue after viewing all data 2024-11-26 22:38:06 +01:00
input_flows.py test: update test framework 2024-12-06 09:24:25 +01:00
README.md
REGISTERED_MARKERS test: update test framework 2024-12-06 09:24:25 +01:00
show_results.py
test_python_support.py
translations.py test: update test framework 2024-12-06 09:24:25 +01:00
tx_cache.py
update_fixtures.py feat(tests): flip the default service for update_fixtures.py ci to github 2024-09-11 12:59:04 +02:00

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://data.trezor.io/dev/firmware/releases/emulators/ 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.