arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-19 22:18:13 +00:00
Code Issues Releases Wiki Activity
e8ee3f7ee1
trezor-firmware/tests
History
grdddj e8ee3f7ee1 chore(tests): adapt click tests for the new recovery flow 
[no changelog]
2023-07-28 09:41:04 +02:00
..
burn_tests chore(tests): add type hints and improve styling in device test files 2022-02-07 14:05:27 +01:00
click_tests chore(tests): adapt click tests for the new recovery flow 2023-07-28 09:41:04 +02:00
connect_tests ci(connect): exclude checkFirmwareAuthenticity test 2022-09-08 12:59:29 +02:00
device_tests fix(tests): fix unstable UI in test_busy_expiry testcase 2023-07-20 10:02:11 +02:00
emulators tests/emulators: fix download_emulators script 2020-07-03 17:33:59 +02:00
fido_tests build(core,legacy): remove gcc, use cc instead of gcc 2022-04-27 15:48:14 +02:00
persistence_tests chore(tests): adapt click tests for the new recovery flow 2023-07-28 09:41:04 +02:00
txcache feat(test): Add device test for migration to CoinJoin account. 2023-02-27 14:22:25 +01:00
ui_tests feat(tests): saving fixtures.results.json file with result hashes after each UI test 2023-07-19 08:58:37 +02:00
upgrade_tests feat(core): new design of recovery dialogs 2023-07-17 15:30:00 +02: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 chore(tests): add type hints to helper test functions 2022-02-07 14:05:27 +01:00
buttons.py chore(tests): improve common code 2023-05-11 21:02:21 +02:00
common.py feat(core): new design of recovery dialogs 2023-07-17 15:30:00 +02:00
conftest.py feat(tests): running master-diff report after each UI test 2023-07-10 11:13:29 +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
gitlab.py feat(tests): add command to automatically update UI fixtures from CI results 2023-07-19 08:58:37 +02:00
input_flows.py chore(all): small design fixes 2023-07-17 15:30:00 +02:00
README.md docs: move docs to root 2019-12-06 12:24:20 +00:00
REGISTERED_MARKERS chore(tests): remove Lisk 2021-08-19 10:25:41 +02:00
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 chore(tests): add SConscript helpers into python support tests 2023-06-19 17:30:00 +02:00
tx_cache.py chore(tests): add type hints to helper test functions 2022-02-07 14:05:27 +01:00
update_fixtures.py feat(tests): add command to automatically update UI fixtures from CI results 2023-07-19 08:58:37 +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.