arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-03 13:08:17 +00:00
Code Issues Releases Wiki Activity
9732f6524a
trezor-firmware/tests
History
grdddj ccf08df07d fix(legacy): show complete taproot QR code without any missing rows/columns 
The QR code will be smaller (only one pixel per module), but scannable anyway.

When the QR code was bigger, but incomplete, Android devices had issues with scanning it.

[no changelog]
2023-02-22 14:48:04 +01: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(core/ui): reset_device copy change 2023-02-17 12:35:19 +01:00
connect_tests ci(connect): exclude checkFirmwareAuthenticity test 2022-09-08 12:59:29 +02:00
device_tests feat(core): ability to not show passphrase coming from host 2023-02-17 12:55:11 +01: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 feat(core/ui): reset_device copy change 2023-02-17 12:35:19 +01:00
txcache feat(core): Verify signatures of all original inputs in replacement transactions. 2022-05-03 22:14:40 +02:00
ui_tests fix(legacy): show complete taproot QR code without any missing rows/columns 2023-02-22 14:48:04 +01:00
upgrade_tests chore(tests): fix click, upgrade and persistence tests for new UI 2022-11-21 14:08:47 +01:00
__init__.py
.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): fix click, upgrade and persistence tests for new UI 2022-11-21 14:08:47 +01:00
common.py refactor(tests): consolidate bitcoin.signtx helper module 2022-02-28 15:45:29 +01:00
conftest.py feat(tests): allow for saving text layout of all screens during UI tests 2023-02-03 16:51:14 +01:00
device_handler.py chore(tests): fix click, upgrade and persistence tests for new UI 2022-11-21 14:08:47 +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 feat(tests): revamp UI test harness 2023-02-02 12:40:39 +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
update_fixtures.py feat(tests): revamp UI test harness 2023-02-02 12:40:39 +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.