mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-19 14:30:31 +00:00

History

grdddj bd6783b1a3 feat(all): increase stability of debug-decision events + parsing JSON from Rust		2023-05-11 21:02:21 +02:00
..
burn_tests
click_tests	feat(all): increase stability of debug-decision events + parsing JSON from Rust	2023-05-11 21:02:21 +02:00
connect_tests
device_tests	chore(tests): update device tests	2023-05-11 21:02:21 +02:00
emulators
fido_tests
persistence_tests	chore(tests): update persistence tests	2023-05-11 21:02:21 +02:00
txcache	feat(test): Add device test for migration to CoinJoin account.	2023-02-27 14:22:25 +01:00
ui_tests	chore(tests): regenerate fixtures.json	2023-05-11 21:02:21 +02:00
upgrade_tests	feat(all): increase stability of debug-decision events + parsing JSON from Rust	2023-05-11 21:02:21 +02:00
__init__.py
.gitignore
bip32.py
buttons.py	chore(tests): improve common code	2023-05-11 21:02:21 +02:00
common.py	chore(tests): improve common code	2023-05-11 21:02:21 +02:00
conftest.py	feat(all): increase stability of debug-decision events + parsing JSON from Rust	2023-05-11 21:02:21 +02:00
device_handler.py	feat(all): increase stability of debug-decision events + parsing JSON from Rust	2023-05-11 21:02:21 +02:00
download_emulators.sh	ci: bump nixpkgs to latest nixpkgs-unstable	2023-04-19 13:05:03 +02:00
emulators.py	feat(tests): allow for coverage report even when emulator is controlled by the tests	2023-03-09 16:50:32 +01:00
input_flows.py	feat(tests): centralize all input flows	2023-05-11 21:02:21 +02:00
README.md	docs: move docs to root	2019-12-06 12:24:20 +00:00
REGISTERED_MARKERS
show_results.py
test_python_support.py
tx_cache.py
update_fixtures.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://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.