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

History

Pavol Rusnak 060df07272 fix(tests): fix trimming of fixture names to avoid collisions		2021-01-20 14:09:27 +01:00
..
burn_tests
click_tests	tests: Fix device tests for streamimg prev_tx after confirmation.	2020-09-04 14:36:39 +02:00
device_tests	feat(core): introduce and enforce limit on label length (fixes #1399 )	2021-01-12 11:22:58 +01:00
emulators
fido_tests	ci: enable editorconfig checks, fix whitespace issues	2020-11-11 14:43:50 +01:00
persistence_tests	core: implement SafetyChecks.PromptTemporarily	2020-09-18 09:02:40 +02:00
txcache	chore(tests): Use strings instead of integers for script_type in tx_cache.	2020-12-22 17:10:33 +01:00
ui_tests	fix(tests): fix trimming of fixture names to avoid collisions	2021-01-20 14:09:27 +01:00
upgrade_tests	style: apply black 20.8b1	2020-09-29 11:30:40 +02:00
__init__.py
.gitignore
bip32.py	feat!(python): drop Mapping protocol support from MessageType	2020-10-30 10:25:51 +01:00
buttons.py	tests: click tests for basic and advanced slip39	2019-11-05 11:13:46 +01:00
common.py	tests: move fixtures to common directory, start with Cardano	2020-09-01 16:14:41 +02:00
conftest.py	feat(tests): dump UI test report as you go	2021-01-11 16:47:59 +01:00
device_handler.py
download_emulators.sh	tests: replace emulators URL	2020-08-27 20:01:23 +02:00
emulators.py	style: apply black 20.8b1	2020-09-29 11:30:40 +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.