History

Martin Milata 662f13136f fix(core/ui): T3T1: get rid of some of the remaining button dialogs		4 months ago
..
burn_tests	…
click_tests	fix(core/ui): T3T1 device tests	4 months ago
connect_tests	…
device_tests	fix(core/ui): T3T1: get rid of some of the remaining button dialogs	4 months ago
emulators	…
fido_tests	…
persistence_tests	fix(core/ui): T3T1 device tests	4 months ago
txcache	feat(test): Add device test for migration to CoinJoin account.	2 years ago
ui_tests	fix(core/ui): T3T1 device tests	4 months ago
upgrade_tests	feat(core): update translation strings	4 months ago
.gitignore	…
README.md	…
REGISTERED_MARKERS	feat(solana): add `get_public_key`	10 months ago
__init__.py	…
bip32.py	…
buttons.py	fix(core/ui): T3T1 device tests	4 months ago
common.py	fix(core/ui): T3T1 device tests	4 months ago
conftest.py	feat(core/ui): T3T1 set new PIN flow	4 months ago
device_handler.py	style(tests): apply isort 5	1 year ago
download_emulators.sh	ci: bump nixpkgs to latest nixpkgs-unstable	1 year ago
emulators.py	feat(tests): allow for coverage report even when emulator is controlled by the tests	2 years ago
github.py	feat(tests): update_fixtures.py: github actions support	6 months ago
gitlab.py	feat(all): implement translations into Trezor	7 months ago
input_flows.py	fix(core/ui): T3T1: get rid of some of the remaining button dialogs	4 months ago
input_flows_helpers.py	fix(core/ui): T3T1 device tests	4 months ago
show_results.py	feat(tests): saving fixtures.results.json file with result hashes after each UI test	1 year ago
test_python_support.py	chore(tests): add SConscript helpers into python support tests	1 year ago
translations.py	tests(translations): always use client version for language blobs	6 months ago
tx_cache.py	…
update_fixtures.py	feat(tests): update_fixtures.py: github actions support	6 months ago

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.