mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-19 14:30:31 +00:00

History

cepetr b1fb876709 fix(core): fix ts3 fonts [no changelog]		2024-04-08 15:38:39 +02:00
..
burn_tests
click_tests	test(core): use internal model names	2024-03-12 20:55:23 +00:00
connect_tests
device_tests	tests(translations): restore test_error_invalid_signature	2024-03-15 13:11:17 +01:00
emulators
fido_tests
persistence_tests	chore(core): change some UI text and TR's screens to match the Figma designs	2023-08-07 15:30:38 +02:00
txcache
ui_tests	fix(core): fix ts3 fonts	2024-04-08 15:38:39 +02:00
upgrade_tests	feat(all): implement translations into Trezor	2024-02-12 14:49:32 +01:00
__init__.py
.gitignore
bip32.py
buttons.py	feat(core): allow for going back to previous word in recovery process	2024-02-19 22:05:04 +01:00
common.py	test(core): use internal model names	2024-03-12 20:55:23 +00:00
conftest.py	test(core): use internal model names	2024-03-12 20:55:23 +00:00
device_handler.py	style(tests): apply isort 5	2023-08-16 13:29:51 +02:00
download_emulators.sh
emulators.py
github.py	feat(tests): update_fixtures.py: github actions support	2024-03-25 11:12:20 +00:00
gitlab.py	feat(all): implement translations into Trezor	2024-02-12 14:49:32 +01:00
input_flows_helpers.py	test(core): add T3T1 support	2024-03-12 20:55:23 +00:00
input_flows.py	test(core): add T3T1 support	2024-03-12 20:55:23 +00:00
README.md
REGISTERED_MARKERS	feat(solana): add `get_public_key`	2023-12-05 22:11:41 +01:00
show_results.py	feat(tests): saving fixtures.results.json file with result hashes after each UI test	2023-07-19 08:58:37 +02:00
test_python_support.py
translations.py	tests(translations): always use client version for language blobs	2024-03-15 13:11:17 +01:00
tx_cache.py
update_fixtures.py	feat(tests): update_fixtures.py: github actions support	2024-03-25 11:12:20 +00:00

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://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.