mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-13 19:18:56 +00:00

History

grdddj e4b5f10223 feat(tests): clicking Info button in (Super)Shamir backup device tests		2022-01-17 12:33:24 +01:00
..
burn_tests
click_tests	style(all): use f-strings for formatting	2021-10-13 11:53:17 +02:00
connect_tests	feat(ci): running connect tests against current branch	2021-12-10 14:18:21 +01:00
device_tests
emulators
fido_tests
persistence_tests
txcache
ui_tests
upgrade_tests	feat(python): introduce Trezor models	2021-12-07 16:55:58 +01:00
__init__.py
.gitignore	feat(ci): running connect tests against current branch	2021-12-10 14:18:21 +01:00
bip32.py	feat!(python): drop Mapping protocol support from MessageType	2020-10-30 10:25:51 +01:00
buttons.py
common.py
conftest.py
device_handler.py
download_emulators.sh
emulators.py	style: apply black 20.8b1	2020-09-29 11:30:40 +02:00
README.md
REGISTERED_MARKERS	chore(tests): remove Lisk	2021-08-19 10:25:41 +02:00
show_results.py	feat(tests): simple javascript-based UI diff review tool	2021-06-23 11:51:18 +02:00
tx_cache.py	fix(tests): TxCache needs to respond to `x in tx_cache`	2021-12-07 16:55:58 +01:00

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.