mirror of
https://github.com/SeedSigner/seedsigner.git
synced 2026-10-05 15:08:25 +00:00
kdmukai
9377f0d9c9
Previously a single button press captured the final image immediately, so the entropy could come from just one frame. Now the live preview must first collect a pool of PREVIEW_POOL_SIZE (50) distinct, non-blank frames before the final image can be taken, and a progress bar/counter shows the user how many have been gathered. - Skip duplicate frames the camera re-hands us (sha256 of the frame bytes) and reject flat single-color frames (getextrema), so only genuinely new frames count toward the pool. - Gate the final capture on a full pool, and rework the held-button guard (is_maybe_still_holding) so a still-held button can't auto-capture the instant the pool fills. Extend tests/test_tools_screens.py and tests/test_flows_tools.py to cover the pool-fill gating and the held-button behavior at capture time.
Running Tests
The tests are designed to be run on non-Raspi hardware.
Setup
On your testing machine you'll have to install:
# general dependencies
pip3 install -r requirements.txt
# test suite dependencies
pip3 install -r tests/requirements.txt
Then make the seedsigner python module visible/importable to the tests by installing it:
pip3 install -e .
Running all tests, calculating overall test coverage
tldr: just run the convenience script from the project root:
./tests/run_full_coverage.sh
Running tests manually
Run the whole test suite:
pytest
Run a specific test file:
pytest tests/test_this_file.py
Run a specific test:
pytest tests/test_this_file.py::test_this_specific_test
Force pytest to show logging output:
pytest tests/test_this_file.py::test_this_specific_test -o log_cli=1
# or (same result)
pytest tests/test_this_file.py::test_this_specific_test --log-cli-level=DEBUG
Annoying complications:
- If you want to see
print()statements that are in a test file, add-s - Better idea: use a proper logger in the test file and use one of the above options to display logs
Screenshot generator
The screenshot generator is meant to mostly be a utility and not really part of the test suite. However,
it is actually implemented to be run by pytest.
see: Screenshot generator README
Generate coverage manually
Run tests and generate test coverage
coverage run -m pytest
The screenshots can generate their own separate coverage report:
coverage run -m pytest tests/screenshot_generator/generator.py --locale es
Show the resulting test coverage details:
coverage report
Generate the interactive html report:
coverage html