mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-19 06:19:27 +00:00

History

matejcik 5385617eda core: increase address length limit to accomodate CRW (fixes #1139 )		2020-08-07 12:45:43 +02:00
..
burn_tests
click_tests	tests: add documentation for click-test recorder	2020-07-10 14:05:52 +02:00
device_tests	core: increase address length limit to accomodate CRW (fixes #1139 )	2020-08-07 12:45:43 +02:00
emulators	tests/emulators: fix download_emulators script	2020-07-03 17:33:59 +02:00
fido_tests
persistence_tests
txcache	tests/sign_tx: Add device tests for transactions with external inputs in bgold, bcash and zcash.	2020-07-03 11:17:19 +02:00
ui_tests	tests: fix test_msg_webauthn on-device	2020-08-05 13:47:35 +02:00
upgrade_tests	core: forbid all settings if not initialized	2020-06-11 18:47:01 +02:00
__init__.py
.gitignore
bip32.py
buttons.py
common.py
conftest.py	tests: make device_handler resilient to interrupting tests	2020-07-10 14:05:52 +02:00
device_handler.py	tests: fix device_handler to be able to enter passphrase via clicks	2020-07-10 14:05:52 +02:00
download_emulators.sh	tests/emulators: fix download_emulators script	2020-07-03 17:33:59 +02:00
emulators.py	core: rename emulator to trezor-emu-core	2020-07-30 15:27:34 +02:00
README.md
REGISTERED_MARKERS
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.