arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-30 01:58:11 +00:00
Code Issues Releases Wiki Activity
4ff2c99f0a
trezor-firmware/tests
History
grdddj a20783731a fix(tests): not use transaction cache in connect tests
2022-09-01 15:02:12 +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 feat(common): Add INFO button to DebugLinkDecision. 2022-01-27 13:15:04 +01:00
connect_tests fix(tests): not use transaction cache in connect tests 2022-09-01 15:02:12 +02:00
device_tests feat(core): add support for Zcash unified addresses 2022-08-30 21:15:49 +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): add type hints and improve styling in device test files 2022-02-07 14:05:27 +01:00
txcache feat(core): Verify signatures of all original inputs in replacement transactions. 2022-05-03 22:14:40 +02:00
ui_tests feat(core): add support for Zcash unified addresses 2022-08-30 21:15:49 +02:00
upgrade_tests chore(tests): add type hints to some non-device tests 2022-02-07 14:05:27 +01: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): add type hints to helper test functions 2022-02-07 14:05:27 +01:00
common.py refactor(tests): consolidate bitcoin.signtx helper module 2022-02-28 15:45:29 +01:00
conftest.py feat(tests): add possibility to run device/UI tests in parallel 2022-08-29 15:47:36 +02:00
device_handler.py chore(tests): add type hints and improve styling in device test files 2022-02-07 14:05:27 +01:00
download_emulators.sh ci(nix): update to latest nixpkgs-unstable 2022-06-21 15:58:06 +02:00
emulators.py feat(tests): add possibility to run device/UI tests in parallel 2022-08-29 15:47:36 +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 chore(tests): add type hints to helper test functions 2022-02-07 14:05:27 +01:00
test_python_support.py feat(tests): add test for supporting older python versions 2022-05-30 14:41:32 +02:00
tx_cache.py chore(tests): add type hints to helper test functions 2022-02-07 14:05:27 +01: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.