arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-18 13:59:17 +00:00
Code Issues Releases Wiki Activity
4d2237b32b
trezor-firmware/tests
History
Rafael Korbas ceea21ec1f feat(cardano): Format stake pool ids as bech32 instead of hex
2021-02-25 16:49:19 +01:00
..
burn_tests
click_tests feat(core): hold homescreen to lock 2021-02-24 00:10:10 +01:00
device_tests test: wait longer for autolock 2021-02-23 14:31:04 +01:00
emulators tests/emulators: fix download_emulators script 2020-07-03 17:33:59 +02:00
fido_tests ci: enable editorconfig checks, fix whitespace issues 2020-11-11 14:43:50 +01:00
persistence_tests tests: use modified protobuf classes correctly 2021-02-10 10:56:52 +01:00
txcache chore(tests): Use strings instead of integers for script_type in tx_cache. 2020-12-22 17:10:33 +01:00
ui_tests feat(cardano): Format stake pool ids as bech32 instead of hex 2021-02-25 16:49:19 +01:00
upgrade_tests style: apply black 20.8b1 2020-09-29 11:30:40 +02:00
__init__.py
.gitignore tests: ignore trezor.log 2020-02-10 12:36:53 +01:00
bip32.py feat!(python): drop Mapping protocol support from MessageType 2020-10-30 10:25:51 +01:00
buttons.py
common.py feat(tests): use JSON descriptions in test identifiers 2021-01-21 15:26:04 +01:00
conftest.py feat(tests): dump UI test report as you go 2021-01-11 16:47:59 +01:00
device_handler.py tests: fix device_handler to be able to enter passphrase via clicks 2020-07-10 14:05:52 +02:00
download_emulators.sh tests: replace emulators URL 2020-08-27 20:01:23 +02:00
emulators.py style: apply black 20.8b1 2020-09-29 11:30:40 +02:00
README.md
REGISTERED_MARKERS all: drop Capricoin support [NO BACKPORT] 2020-03-20 14:19:30 +00:00
tx_cache.py python: move json_to_tx to btc.from_json, add test cases 2020-03-26 11:30:06 +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://firmware.corp.sldev.cz/upgrade_tests/ 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.