History

grdddj ccf08df07d fix(legacy): show complete taproot QR code without any missing rows/columns The QR code will be smaller (only one pixel per module), but scannable anyway. When the QR code was bigger, but incomplete, Android devices had issues with scanning it. [no changelog]		1 year ago
..
burn_tests	chore(tests): add type hints and improve styling in device test files	2 years ago
click_tests	feat(core/ui): reset_device copy change	1 year ago
connect_tests	ci(connect): exclude checkFirmwareAuthenticity test	2 years ago
device_tests	feat(core): ability to not show passphrase coming from host	1 year ago
emulators	tests/emulators: fix download_emulators script	4 years ago
fido_tests	build(core,legacy): remove gcc, use cc instead of gcc	2 years ago
persistence_tests	feat(core/ui): reset_device copy change	1 year ago
txcache	feat(core): Verify signatures of all original inputs in replacement transactions.	2 years ago
ui_tests	fix(legacy): show complete taproot QR code without any missing rows/columns	1 year ago
upgrade_tests	chore(tests): fix click, upgrade and persistence tests for new UI	1 year ago
.gitignore	fix(tests): not use transaction cache in connect tests	2 years ago
README.md	docs: move docs to root	4 years ago
REGISTERED_MARKERS	chore(tests): remove Lisk	3 years ago
__init__.py	tests: start moving common functions to top level	5 years ago
bip32.py	chore(tests): add type hints to helper test functions	2 years ago
buttons.py	chore(tests): fix click, upgrade and persistence tests for new UI	1 year ago
common.py	refactor(tests): consolidate bitcoin.signtx helper module	2 years ago
conftest.py	feat(tests): allow for saving text layout of all screens during UI tests	1 year ago
device_handler.py	chore(tests): fix click, upgrade and persistence tests for new UI	1 year ago
download_emulators.sh	ci(nix): update to latest nixpkgs-unstable	2 years ago
emulators.py	feat(tests): add possibility to run device/UI tests in parallel	2 years ago
show_results.py	feat(tests): revamp UI test harness	1 year ago
test_python_support.py	feat(tests): add test for supporting older python versions	2 years ago
tx_cache.py	chore(tests): add type hints to helper test functions	2 years ago
update_fixtures.py	feat(tests): revamp UI test harness	1 year 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.