arno
/
trezor-firmware
mirror of https://github.com/trezor/trezor-firmware.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'tychovrahe/coresplit/merged'
${ noResults }
trezor-firmware/tests
History
JoeGruff d2a2ac2178
decred: Add input_derive_script. 		2 weeks ago
..
burn_tests chore(tests): add type hints and improve styling in device test files 3 years ago
click_tests feat(core): ask for 20/33 words to unlock backup 3 weeks ago
connect_tests ci(connect): exclude checkFirmwareAuthenticity test 2 years ago
device_tests decred: Add input_derive_script. 2 weeks ago
emulators tests/emulators: fix download_emulators script 4 years ago
fido_tests build(core,legacy): remove gcc, use cc instead of gcc 2 years ago
persistence_tests refactor(core): send out ButtonRequest name 2 months ago
txcache decred: Add input_derive_script. 2 weeks ago
ui_tests feat(core/translations): add it, pt 2 weeks ago
upgrade_tests feat: Remove display_random feature. 3 weeks ago
.gitignore fix(tests): not use transaction cache in connect tests 2 years ago
README.md docs: move docs to root 5 years ago
REGISTERED_MARKERS feat(solana): add `get_public_key` 10 months ago
__init__.py tests: start moving common functions to top level 5 years ago
bip32.py chore(tests): add type hints to helper test functions 3 years ago
buttons.py feat(core/mercury): impl flow_request_passphrase 4 weeks ago
common.py feat(core): improve repeated backup 3 months ago
conftest.py feat(tests): reduce ui error spam 3 months ago
device_handler.py style(tests): apply isort 5 1 year ago
download_emulators.sh ci: bump nixpkgs to latest nixpkgs-unstable 1 year ago
emulators.py feat(tests): allow for coverage report even when emulator is controlled by the tests 2 years ago
github.py feat(core/translations): add it, pt 2 weeks ago
gitlab.py feat(all): implement translations into Trezor 7 months ago
input_flows.py fix(core/ui/mercury): FIDO2 layouts 2 weeks ago
input_flows_helpers.py chore(core): update fixtures and fix style 2 weeks ago
show_results.py feat(tests): saving fixtures.results.json file with result hashes after each UI test 1 year ago
test_python_support.py chore(tests): add SConscript helpers into python support tests 1 year ago
translations.py chore(core): support T3B1 for translation blobs 2 weeks ago
tx_cache.py chore(tests): add type hints to helper test functions 3 years ago
update_fixtures.py feat(tests): update_fixtures.py: github run_id 3 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.