History

grdddj a4034097d6 feat(tests): number the screens in UI test reports, give unique IDs to images [no changelog]		11 months ago
..
burn_tests	…
click_tests	chore(tests): adapt click tests for the new recovery flow	11 months ago
connect_tests	…
device_tests	chore(tests): refactor recovery input flows	11 months ago
emulators	…
fido_tests	…
persistence_tests	chore(tests): adapt click tests for the new recovery flow	11 months ago
txcache	…
ui_tests	feat(tests): number the screens in UI test reports, give unique IDs to images	11 months ago
upgrade_tests	chore(tests): use special recovery functions for upgrade tests	11 months ago
.gitignore	…
README.md	…
REGISTERED_MARKERS	…
__init__.py	…
bip32.py	…
buttons.py	…
common.py	chore(tests): refactor recovery input flows	11 months ago
conftest.py	feat(tests): running master-diff report after each UI test	12 months ago
device_handler.py	…
download_emulators.sh	…
emulators.py	…
gitlab.py	feat(tests): add command to automatically update UI fixtures from CI results	12 months ago
input_flows.py	chore(tests): refactor recovery input flows	11 months ago
input_flows_helpers.py	chore(tests): refactor recovery input flows	11 months ago
show_results.py	feat(tests): saving fixtures.results.json file with result hashes after each UI test	12 months ago
test_python_support.py	chore(tests): add SConscript helpers into python support tests	1 year ago
tx_cache.py	…
update_fixtures.py	feat(tests): add command to automatically update UI fixtures from CI results	12 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.