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

History

grdddj f3c4f1e867 chore(tests): regenerate fixtures [no changelog]		2023-09-19 11:48:58 +02:00
..
burn_tests
click_tests	chore(core): change error screens according to design	2023-09-01 10:27:48 +02:00
connect_tests
device_tests	chore(tests): account for T2B1 sending extra ConfirmOutput BR in device tests	2023-09-15 09:50:21 +02:00
emulators
fido_tests
persistence_tests	chore(core): change some UI text and TR's screens to match the Figma designs	2023-08-07 15:30:38 +02:00
txcache
ui_tests	chore(tests): regenerate fixtures	2023-09-19 11:48:58 +02:00
upgrade_tests	chore(tests): use special recovery functions for upgrade tests	2023-07-28 09:41:04 +02:00
__init__.py
.gitignore
bip32.py
buttons.py
common.py	feat(tests): Add AuthenticateDevice test.	2023-09-13 15:45:48 +02:00
conftest.py	style(tests): apply isort 5	2023-08-16 13:29:51 +02:00
device_handler.py	style(tests): apply isort 5	2023-08-16 13:29:51 +02:00
download_emulators.sh
emulators.py
gitlab.py	feat(tests): notify about failed tests when updating fixtures from CI	2023-08-09 16:07:27 +02:00
input_flows_helpers.py	chore(tests): refactor Ethereum input flows	2023-09-04 13:50:30 +02:00
input_flows.py	chore(tests): accounting for the extra T2B1 buton request in input flows	2023-09-15 09:50:21 +02:00
README.md
REGISTERED_MARKERS
show_results.py	feat(tests): saving fixtures.results.json file with result hashes after each UI test	2023-07-19 08:58:37 +02:00
test_python_support.py
tx_cache.py
update_fixtures.py	feat(tests): allow for removing missing tests when updating UI fixtures from CI	2023-09-15 09:50:21 +02: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.