arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-22 15:38:11 +00:00
Code Issues Releases Wiki Activity
1523f09b37
trezor-firmware/tests
History
Andrew Kozlik 6cc44b133c tests/webauthn: Account for the increased limit on the number of resident credentials.
2019-11-01 16:14:16 +01:00
..
burn_tests tests: move burn tests to root 2019-08-12 12:57:25 +02:00
click_tests tests/click: refactor recovery 2019-10-25 14:38:10 +00:00
device_tests tests/webauthn: Account for the increased limit on the number of resident credentials. 2019-11-01 16:14:16 +01:00
emulators tests/upgrade tests: patch emulators on NixOS 2019-10-22 13:59:26 +02:00
fido_tests ci: add fido2 tests to ci 2019-10-18 16:54:00 +02:00
persistence_tests tests: move persistence tests to its own folder 2019-10-25 12:04:14 +00:00
txcache tests: move device tests to top-level 2019-08-12 12:57:25 +02:00
upgrade_tests tests: add upgrade test for recovery 2019-10-25 14:38:10 +00:00
__init__.py tests: start moving common functions to top level 2019-09-12 14:29:33 +02:00
buttons.py tests: fix grid34 2019-10-22 17:06:49 +02:00
common.py tests: add upgrade test for recovery 2019-10-25 14:38:10 +00:00
conftest.py tests: rename background.py to device_handler.py 2019-10-22 17:06:49 +02:00
device_handler.py core: improve emulator wrapper 2019-10-22 17:06:49 +02:00
download_emulators.sh tests/upgrade tests: patch emulators on NixOS 2019-10-22 13:59:26 +02:00
emulators.py core: improve emulator wrapper 2019-10-22 17:06:49 +02:00
README.md tests: update README 2019-10-25 12:22:20 +00:00
REGISTERED_MARKERS tests: add multisig marker 2019-10-22 14:32:38 +00:00
trezor.sdcard.gz core: improve emulator wrapper 2019-10-22 17:06:49 +02:00
tx_cache.py tests: start moving common functions to top level 2019-09-12 14:29:33 +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 the README for instructions how to run it.

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 README 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.