History

M1nd3r 2c61321857 fix(core): fix conflicts and style, part 1 [no changelog]		4 weeks ago
..
burn_tests	…
click_tests	fix(core): fix conflicts and style, part 1	4 weeks ago
connect_tests	…
device_tests	chore(python): improve recovery type deprecation warning	4 weeks ago
emulators	…
fido_tests	…
persistence_tests	tests: fix small irregularities	4 weeks ago
txcache	…
ui_tests	fixup! chore: update fixtures	4 weeks ago
upgrade_tests	tests: use read_layout everywhere	4 weeks ago
.gitignore	…
README.md	…
REGISTERED_MARKERS	…
__init__.py	…
bip32.py	…
buttons.py	…
common.py	tests: fix small irregularities	4 weeks ago
conftest.py	fix(core): fix conflicts and style, part 1	4 weeks ago
device_handler.py	fix(tests): stop waiting for background task after a timeout	4 weeks ago
download_emulators.sh	…
emulators.py	…
github.py	feat(tests): update_fixtures.py: github run_id	4 months ago
gitlab.py	…
input_flows.py	fixup! tests: fix small irregularities	4 weeks ago
input_flows_helpers.py	fix(core): fix conflicts and style, part 1	4 weeks ago
show_results.py	…
test_python_support.py	…
translations.py	feat(core): deal with non-breaking spaces	2 months ago
tx_cache.py	…
update_fixtures.py	feat(tests): update_fixtures.py: github run_id	4 months 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://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.