test(prodtest): mention prodtest-tests in docs
What the developer wrote
Authored by M1nd3r
test(prodtest): mention prodtest-tests in docs
[no changelog]
What changed, and why it matters
This commit only adds documentation. It updates the test documentation to mention how to run production-test firmware tests. There is no code change and no security relevance.
No action needed; this is a documentation-only change with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a new ‘Prodtest tests’ section to docs/tests/index.md describing the prodtest test suite, its location, isolation, and the make target to run it. No source code, build scripts, or test logic were modified.
Changed components
docs/tests/index.mdInspect captured patch +10 / −0
diff --git a/docs/tests/index.md b/docs/tests/index.md
index b752e41c..150ab6f1 100644
--- a/docs/tests/index.md
+++ b/docs/tests/index.md
@@ -38,3 +38,13 @@ See the [upgrade-tests.md](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.
+
+## Prodtest tests
+
+These tests test the production test firmware (prodtest) CLI against the prodtest emulator. The tests are located in `prodtest_tests/` and have their own `conftest.py`, isolated from the device-test suite.
+
+Run them with:
+
+```sh
+make -C core test_emu_prodtest
+```
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.