History

grdddj 5dc193a552 chore(tests): regenerate fixtures [no changelog]		8 months ago
..
burn_tests	chore(tests): add type hints and improve styling in device test files	3 years ago
click_tests	fix(tests): Safe 3 model name	12 months ago
connect_tests	ci(connect): exclude checkFirmwareAuthenticity test	2 years ago
device_tests	chore(solana): add device tests for predefined txs	10 months ago
emulators	tests/emulators: fix download_emulators script	4 years ago
fido_tests	…
persistence_tests	…
txcache	…
ui_tests	chore(tests): regenerate fixtures	8 months ago
upgrade_tests	…
.gitignore	fix(tests): not use transaction cache in connect tests	2 years ago
README.md	…
REGISTERED_MARKERS	feat(solana): add `get_public_key`	10 months ago
__init__.py	tests: start moving common functions to top level	5 years ago
bip32.py	…
buttons.py	…
common.py	feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`.	10 months ago
conftest.py	fix(tests): Safe 3 model name	12 months ago
device_handler.py	…
download_emulators.sh	…
emulators.py	…
gitlab.py	…
input_flows.py	feat(tests): add test for going back from Ethereum summary page	10 months ago
input_flows_helpers.py	feat(tests): add test for going back from Ethereum summary page	10 months ago
show_results.py	…
test_python_support.py	…
tx_cache.py	chore(tests): add type hints to helper test functions	3 years ago
update_fixtures.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://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.