SeedSigner

This commit only changes test code. It tightens an existing unit test so it actually exercises the cache read path, and improves comments and docstrings. No production code was modified, so it cannot introduce or fix a security vulnerability in the application itself.

This commit only changes a test file. It makes the test measure the size of a temporary cache while the code is running, instead of reading the cache afterward. This is a test-quality improvement, not a security fix.

This is a test-only fix for a CI screenshot generator. It stops the test suite from crashing when GitHub's public API rate-limits an unauthenticated version-lookup request. There is no security vulnerability in the actual SeedSigner wallet or user-facing code; the change only adds a fallback placeholder so screenshots keep rendering during automated tests.

This commit only changes test files. It refactors how SettingsQR test data is built by introducing a shared base class so tests use the current default settings automatically instead of hardcoded strings. There is no change to the actual application code that users run, so it cannot directly affect security or introduce a vulnerability.

This commit only updates the GitHub pull request template, which is a form contributors fill out when submitting code changes. It does not change any actual application code, so it has no direct security impact on the SeedSigner software or its users.

This commit only adjusts whitespace in a test screenshot generator file so that the opening parentheses line up visually. No code behavior, logic, or security-sensitive content changed.

This commit only rewords comments in two test helper files. No code behavior was changed, so it has no security relevance.

This commit is a trivial cleanup of a test file. It removes an unused import (SettingsEntry), deletes a debug print statement, and fixes some whitespace. There is no change to the actual application code that handles seeds, keys, or user settings, so it has no security relevance.

This commit adds one extra test case (an empty list `[]`) to an existing unit test that checks how the SeedSigner settings code handles empty values. It is purely a test-file change and does not modify any production code, user-facing behavior, or security-sensitive logic.

This commit removes a helper function used only in a screenshot-generation test script. The deleted code fetched the latest SeedSigner release version from GitHub and temporarily overwrote version data so screenshots would display consistent version information. It is a test-only cleanup with no effect on the actual SeedSigner application or its security.

This commit only rewords comments and docstrings in test helper files that generate screenshots. No code behavior was changed, so it has no security relevance.

This commit moves a GitHub Actions environment variable definition from inside a single test step to the top of the workflow file. It is a routine CI configuration cleanup with no apparent security relevance.

This commit only updates a test file to match how GitHub Actions environment variables are named. It does not change the actual application code that users run, and there is no security issue visible here.

This commit removes a temporary workaround (mocking the operating system type) from a single automated test file. It does not change any production code, user-facing behavior, or security-sensitive logic. The change simply makes the test rely on the real environment instead of pretending to be a specific OS.

This is a tiny code cleanup in a helper script that writes a version information file. It removes four comment lines and combines two variable assignments into one line. There is no functional change and no security relevance.

This is a one-line bugfix in a build helper script. A previous code rename left a reference to an old method name, which would have caused the script to crash. The patch simply points the script to the correct new method name. There is no security-relevant change visible in the diff.

This is a one-line bugfix in a test helper script that generates screenshots. The change swaps a public method call for directly clearing an internal singleton variable. It only affects the screenshot generator's cleanup routine and does not appear to be a security fix for user-facing code.

This commit only changes a test file that checks how the software reports its version number when running inside GitHub Actions. It does not change the actual version-detection code or any security-sensitive behavior. There is no security issue here.

This commit only changes test code in tests/test_version.py. It fixes test bugs by adding a fixture that controls an environment variable during tests and updates several test assertions to call the correct utility class (VersionUtils instead of Version). There are no changes to the actual application code that users run, so this has no direct security impact on the SeedSigner device or software.

This commit fixes a minor test-only bug. The test file was calling a unittest method (self.skipTest) inside a pytest-based test, which does not work correctly. The change replaces it with pytest.skip and adjusts imports. It only affects how one test is skipped when there is no Git directory; it does not change any production code or security behavior.

This is a one-line correction in a test file. The test was checking that a 'passphrase' setting was NOT included in parsed QR-code settings, but the intended behavior is that it SHOULD be included. The change fixes the test assertion to match the actual expected behavior. It does not change any production code and has no direct security impact on users.

This commit only updates test files to remove references to an obsolete 'xpub_export' setting. It does not change any production code, user-facing behavior, or security controls. There is no security issue in this patch.

This commit only changes test code. It updates a unit test so that it checks both single-signature and multi-signature PSBT inputs, and it makes the fingerprint assertions more precise by distinguishing public keys that belong to the current seed from those that don't. There is no change to the actual application code that handles seeds or transactions.

This commit only changes a test file. It renames a test, tightens some assertions, and temporarily removes multisig test cases from a loop so only single-signature inputs are exercised. There is no change to the actual PSBT parsing or wallet code, so it does not fix or introduce a security issue by itself.

This commit only updates the project's test suite. It adds a new screenshot configuration for a warning screen and adds one new assertion checking a default setting value. There are no changes to production code, no security fixes, and no behavior changes that affect users.