mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-15 20:19:23 +00:00

History

grdddj 89b905a349 fix(tests): make master_diff more reliable [no changelog]		2023-02-17 10:28:35 +01:00
..
burn_tests
click_tests	fix(tests): increase delay between click test button presses	2023-02-10 13:03:29 +01:00
connect_tests	ci(connect): exclude checkFirmwareAuthenticity test	2022-09-08 12:59:29 +02:00
device_tests	feat(core): EIP712 signing shows the ethereum address at the beginning	2023-02-14 15:30:05 +01:00
emulators
fido_tests
persistence_tests	refactor(core/rust/ui): homescreen layouts	2022-12-13 17:15:15 +01:00
txcache
ui_tests	fix(tests): make master_diff more reliable	2023-02-17 10:28:35 +01:00
upgrade_tests	chore(tests): fix click, upgrade and persistence tests for new UI	2022-11-21 14:08:47 +01:00
__init__.py	tests: start moving common functions to top level	2019-09-12 14:29:33 +02:00
.gitignore	fix(tests): not use transaction cache in connect tests	2022-09-01 15:02:12 +02:00
bip32.py
buttons.py	chore(tests): fix click, upgrade and persistence tests for new UI	2022-11-21 14:08:47 +01:00
common.py
conftest.py	feat(tests): allow for saving text layout of all screens during UI tests	2023-02-03 16:51:14 +01:00
device_handler.py	chore(tests): fix click, upgrade and persistence tests for new UI	2022-11-21 14:08:47 +01:00
download_emulators.sh	ci(nix): update to latest nixpkgs-unstable	2022-06-21 15:58:06 +02:00
emulators.py	feat(tests): add possibility to run device/UI tests in parallel	2022-08-29 15:47:36 +02:00
README.md
REGISTERED_MARKERS	chore(tests): remove Lisk	2021-08-19 10:25:41 +02:00
show_results.py	feat(tests): revamp UI test harness	2023-02-02 12:40:39 +01:00
test_python_support.py
tx_cache.py
update_fixtures.py	feat(tests): revamp UI test harness	2023-02-02 12:40:39 +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://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.