docs(test): update docs for upgrade tests
What changed, and why it matters
This commit only updates two documentation files. It changes the URL path for emulator download fixtures and clarifies that users should specify a device model when running the download script. There is no code change and no security relevance.
No security action needed. Treat as routine documentation maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies docs/tests/index.md and docs/tests/upgrade-tests.md. It updates the emulator fixtures URL from …/emulators/ to …/emulators-new/ and updates the download_emulators.sh invocation to require a {model} argument. No firmware, test logic, build, or cryptographic code is touched.
Changed components
docs/tests/index.mddocs/tests/upgrade-tests.mdInspect captured patch +3 / −3
diff --git a/docs/tests/index.md b/docs/tests/index.md
index 57ff03b06..b752e41c9 100644
--- a/docs/tests/index.md
+++ b/docs/tests/index.md
@@ -31,7 +31,7 @@ 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.
+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-new/ which can be downloaded using the `download_emulators.sh` script.
See the [upgrade-tests.md](upgrade-tests.md) for instructions how to run it.
diff --git a/docs/tests/upgrade-tests.md b/docs/tests/upgrade-tests.md
index 6c5f7106f..84b3130f8 100644
--- a/docs/tests/upgrade-tests.md
+++ b/docs/tests/upgrade-tests.md
@@ -7,10 +7,10 @@ uv sync
source .venv/bin/activate
```
-2. Download the emulators, if you have not already:
+2. Download the emulators for the models you want to test, if you have not already:
```sh
-tests/download_emulators.sh
+tests/download_emulators.sh {model}
```
3. And run the tests using pytest:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.