arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2025-01-03 12:00:59 +00:00
Code Issues Releases Wiki Activity
cbe4e0e725
trezor-firmware/tests
History
matejcik a58823cc0c refactor(python): rework trezorlib protobuf codec 
API-compatibility with the original one is retained.

Now that we don't need to keep code parity with core, we could do some
changes that make life easier.

All generated classes are now in one file. This makes github diffs more
readable, at the cost of somewhat complicating inspecting individual
classes; however, that is something we shouldn't be doing anyway.

Enums are now implemented as enum.IntEnum.

The original class-level FIELDS member was restored.

Each field is now defined via protobuf.Field, which is easier to work
with in the codec, AND we're not stuffing defaults and flags into the
same field.
2021-06-08 09:55:19 +02:00
..
burn_tests tests: move burn tests to root 2019-08-12 12:57:25 +02:00
click_tests refactor(core): no implicit spaces in render_text 2021-03-30 22:34:01 +02:00
device_tests refactor(python): rework trezorlib protobuf codec 2021-06-08 09:55:19 +02:00
emulators tests/emulators: fix download_emulators script 2020-07-03 17:33:59 +02:00
fido_tests ci: enable editorconfig checks, fix whitespace issues 2020-11-11 14:43:50 +01:00
persistence_tests feat(core): avoid restarting session for select messages (fixes #1631) 2021-06-01 14:07:29 +02:00
txcache test: Add device test for replacement transaction with OP_RETURN output. 2021-03-24 22:06:41 +01:00
ui_tests test(device): Test safety checks on T1. 2021-05-24 17:47:43 +02:00
upgrade_tests refactor(python): rework trezorlib protobuf codec 2021-06-08 09:55:19 +02:00
__init__.py tests: start moving common functions to top level 2019-09-12 14:29:33 +02:00
.gitignore tests: ignore trezor.log 2020-02-10 12:36:53 +01:00
bip32.py feat!(python): drop Mapping protocol support from MessageType 2020-10-30 10:25:51 +01:00
buttons.py tests: click tests for basic and advanced slip39 2019-11-05 11:13:46 +01:00
common.py refactor(core): convert parts of apps.management to layouts 2021-03-30 22:34:01 +02:00
conftest.py feat(tests): dump UI test report as you go 2021-01-11 16:47:59 +01:00
device_handler.py tests: fix device_handler to be able to enter passphrase via clicks 2020-07-10 14:05:52 +02:00
download_emulators.sh tests: replace emulators URL 2020-08-27 20:01:23 +02:00
emulators.py style: apply black 20.8b1 2020-09-29 11:30:40 +02:00
README.md docs: move docs to root 2019-12-06 12:24:20 +00:00
REGISTERED_MARKERS all: drop Capricoin support [NO BACKPORT] 2020-03-20 14:19:30 +00:00
tx_cache.py python: move json_to_tx to btc.from_json, add test cases 2020-03-26 11:30:06 +01:00

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.