arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-12 18:49:07 +00:00
Code Issues Releases Wiki Activity
121ed1f530
trezor-firmware/tests
History
obrusvit ca469784ba chore(core): update fixtures.json 
Update as a part of T3T1 recovery share success screens and adding a new
test of aborting the recovery process between shares for all models.

[no changelog]
2024-07-31 11:36:32 +02:00
..
burn_tests
click_tests fix(tests): tweak pressed button in repeated backup 2024-06-06 14:00:13 +02:00
connect_tests ci(connect): exclude checkFirmwareAuthenticity test 2022-09-08 12:59:29 +02:00
device_tests tests: UI test of cancel recovery between shares 2024-07-31 11:36:32 +02:00
emulators
fido_tests
persistence_tests refactor(core): send out ButtonRequest name 2024-07-19 11:28:07 +03:00
txcache feat(test): Add device test for migration to CoinJoin account. 2023-02-27 14:22:25 +01:00
ui_tests chore(core): update fixtures.json 2024-07-31 11:36:32 +02:00
upgrade_tests chore(core): rename recovery type & kind and tweak feature flags 2024-06-05 12:35:09 +03:00
__init__.py
.gitignore fix(tests): not use transaction cache in connect tests 2022-09-01 15:02:12 +02:00
bip32.py
buttons.py fix(core/ui): T3T1 device tests 2024-05-31 11:59:52 +00:00
common.py feat(core): improve repeated backup 2024-06-06 14:00:13 +02:00
conftest.py feat(tests): reduce ui error spam 2024-06-06 14:00:13 +02:00
device_handler.py style(tests): apply isort 5 2023-08-16 13:29:51 +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
github.py feat(tests): update_fixtures.py: github run_id 2024-06-06 14:43:51 +00:00
gitlab.py feat(all): implement translations into Trezor 2024-02-12 14:49:32 +01:00
input_flows_helpers.py tests: UI test of cancel recovery between shares 2024-07-31 11:36:32 +02:00
input_flows.py tests: UI test of cancel recovery between shares 2024-07-31 11:36:32 +02:00
README.md
REGISTERED_MARKERS feat(solana): add get_public_key 2023-12-05 22:11:41 +01: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
translations.py feat(core): deal with non-breaking spaces 2024-07-30 18:48:01 +03:00
tx_cache.py
update_fixtures.py feat(tests): update_fixtures.py: github run_id 2024-06-06 14:43:51 +00: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.