History

matejcik 34913a328a all: disallow most RecoveryDevice fields in dry-run (fixes #666 )		5 years ago
..
burn_tests	tests: move burn tests to root	5 years ago
click_tests	tests: improve clicktests	5 years ago
device_tests	all: disallow most RecoveryDevice fields in dry-run (fixes #666 )	5 years ago
emulators	tests/upgrade tests: patch emulators on NixOS	5 years ago
fido_tests	tests/fido_tests: add simple device tests using libfido2	5 years ago
persistence_tests	tests/persistence: extend recovery test to test a full recovery	5 years ago
txcache	tests: move device tests to top-level	5 years ago
upgrade_tests	python: rename webauthn and u2f to fido	5 years ago
README.md	tests: update README	5 years ago
REGISTERED_MARKERS	tests: add multisig marker	5 years ago
__init__.py	tests: start moving common functions to top level	5 years ago
buttons.py	tests: click tests for basic and advanced slip39	5 years ago
common.py	tests: add upgrade test for recovery	5 years ago
conftest.py	tests: make {needs,no}_backup flags available in test suite	5 years ago
device_handler.py	core: improve emulator wrapper	5 years ago
download_emulators.sh	tests/upgrade tests: patch emulators on NixOS	5 years ago
emulators.py	core: improve emulator wrapper	5 years ago
trezor.sdcard.gz	core: improve emulator wrapper	5 years ago
tx_cache.py	tests: start moving common functions to top level	5 years ago

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.