41f980b3a3
The global layout related changes were wrong for T1 where debuglink behavior is significantly different; in particular, it is not always possible to communicate over debuglink. This change reverts to the old behavior for T1B1 and keeps the new one only for core-based models. |
||
|---|---|---|
| .. | ||
| burn_tests | ||
| click_tests | ||
| connect_tests | ||
| device_tests | ||
| emulators | ||
| fido_tests | ||
| persistence_tests | ||
| txcache | ||
| ui_tests | ||
| upgrade_tests | ||
| __init__.py | ||
| .gitignore | ||
| bip32.py | ||
| buttons.py | ||
| common.py | ||
| conftest.py | ||
| device_handler.py | ||
| download_emulators.sh | ||
| emulators.py | ||
| github.py | ||
| gitlab.py | ||
| input_flows_helpers.py | ||
| input_flows.py | ||
| README.md | ||
| REGISTERED_MARKERS | ||
| show_results.py | ||
| test_python_support.py | ||
| translations.py | ||
| tx_cache.py | ||
| update_fixtures.py | ||
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.