History

Martin Milata b5710b820a docs(core): replace Purpose48 with BIP-48 https://github.com/bitcoin/bips/blob/master/bip-0048.mediawiki		3 years ago
..
burn_tests	…
click_tests	refactor(core/ui): use new_lines=False in layouts	3 years ago
device_tests	docs(core): replace Purpose48 with BIP-48	3 years ago
emulators	…
fido_tests	ci: enable editorconfig checks, fix whitespace issues	4 years ago
persistence_tests	feat(core): avoid restarting session for select messages (fixes #1631 )	3 years ago
txcache	test: Add device test for replacement transaction with OP_RETURN output.	3 years ago
ui_tests	refactor(core/ui): do not use parameter for styling in get_next_u2f_counter	3 years ago
upgrade_tests	refactor(python): rework trezorlib protobuf codec	3 years ago
.gitignore	…
README.md	…
REGISTERED_MARKERS	…
__init__.py	…
bip32.py	…
buttons.py	…
common.py	fix(tests): auto-swipe by using only ButtonRequest.pages	3 years ago
conftest.py	feat(tests): reuse same client instance across test session	3 years ago
device_handler.py	…
download_emulators.sh	…
emulators.py	…
show_results.py	feat(tests): simple javascript-based UI diff review tool	3 years ago
tx_cache.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://firmware.corp.sldev.cz/upgrade_tests/ 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.