1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-20 14:59:06 +00:00
trezor-firmware/tests
obrusvit c5f9fadbd1 fix(core/mercury): show remaining shares
This commit enables showing "Remaining shares" from the context menu
during recovery process. This is only shown during super-shamir.
2024-09-03 14:20:34 +02:00
..
burn_tests
click_tests feat(core): ask for 20/33 words to unlock backup 2024-08-29 16:01:13 +02:00
connect_tests
device_tests fix(core/mercury): show remaining shares 2024-09-03 14:20:34 +02:00
emulators
fido_tests
persistence_tests refactor(core): send out ButtonRequest name 2024-07-19 11:28:07 +03:00
txcache
ui_tests fix(core/mercury): show remaining shares 2024-09-03 14:20:34 +02:00
upgrade_tests feat: Remove display_random feature. 2024-08-27 19:33:23 +02:00
__init__.py
.gitignore
bip32.py
buttons.py feat(core/mercury): impl flow_request_passphrase 2024-08-22 00:47:15 +02:00
common.py feat(core): improve repeated backup 2024-06-06 14:00:13 +02:00
conftest.py feat(tests): reduce ui error spam 2024-06-06 14:00:13 +02:00
device_handler.py
download_emulators.sh
emulators.py
github.py feat(tests): update_fixtures.py: github run_id 2024-06-06 14:43:51 +00:00
gitlab.py feat(all): implement translations into Trezor 2024-02-12 14:49:32 +01:00
input_flows_helpers.py fix(core/mercury): show remaining shares 2024-09-03 14:20:34 +02:00
input_flows.py fix(core/ui/mercury): FIDO2 layouts 2024-09-02 19:36:25 +02:00
README.md
REGISTERED_MARKERS feat(solana): add get_public_key 2023-12-05 22:11:41 +01:00
show_results.py
test_python_support.py
translations.py chore(core): support T3B1 for translation blobs 2024-09-03 10:35:14 +02:00
tx_cache.py
update_fixtures.py feat(tests): update_fixtures.py: github run_id 2024-06-06 14:43:51 +00: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.