History

Andrew Kozlik 3be0138aae test: Add device test for replacement transaction with invalid original signature.		3 years ago
..
burn_tests	tests: move burn tests to root	5 years ago
click_tests	tests: Fix device tests for streamimg prev_tx after confirmation.	4 years ago
device_tests	test: Add device test for replacement transaction with invalid original signature.	3 years ago
emulators	tests/emulators: fix download_emulators script	4 years ago
fido_tests	ci: enable editorconfig checks, fix whitespace issues	4 years ago
persistence_tests	core: implement SafetyChecks.PromptTemporarily	4 years ago
txcache	test: Add device test for RBF finalization.	3 years ago
ui_tests	fix(tests): remove dropped EOSClassic test case	3 years ago
upgrade_tests	style: apply black 20.8b1	4 years ago
.gitignore	tests: ignore trezor.log	4 years ago
README.md	docs: move docs to root	4 years ago
REGISTERED_MARKERS	all: drop Capricoin support [NO BACKPORT]	4 years ago
__init__.py	tests: start moving common functions to top level	5 years ago
bip32.py	feat!(python): drop Mapping protocol support from MessageType	4 years ago
buttons.py	tests: click tests for basic and advanced slip39	5 years ago
common.py	tests: move fixtures to common directory, start with Cardano	4 years ago
conftest.py	feat(core): add experimental_features setting	4 years ago
device_handler.py	tests: fix device_handler to be able to enter passphrase via clicks	4 years ago
download_emulators.sh	tests: replace emulators URL	4 years ago
emulators.py	style: apply black 20.8b1	4 years ago
tx_cache.py	python: move json_to_tx to btc.from_json, add test cases	4 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 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.