Skip to content

feat: added hypothesis and pytest-benchmark to tests/requirements.txt#899

Open
S1DDHEY wants to merge 1 commit intoSeedSigner:devfrom
S1DDHEY:feat/hypothesis-pytest-benchmark
Open

feat: added hypothesis and pytest-benchmark to tests/requirements.txt#899
S1DDHEY wants to merge 1 commit intoSeedSigner:devfrom
S1DDHEY:feat/hypothesis-pytest-benchmark

Conversation

@S1DDHEY
Copy link
Copy Markdown

@S1DDHEY S1DDHEY commented Apr 5, 2026

Description

Problem or Issue being addressed

The test suite currently relies entirely on hand-crafted fixtures and test vectors. There is no property-based testing framework or benchmarking harness available for contributors to use. This is a prerequisite for introducing property-based test coverage for critical modules like PSBTParser, DecodeQR, and embit_utils.

Solution

Added hypothesis==6.151.10 and pytest-benchmark==5.2.3 to tests/requirements.txt, following the existing convention of pinning exact versions. Both packages integrate cleanly with the existing pytest==7.4.2 setup and introduce no regressions, all 145 existing tests continue to pass.

Additional Information

This lays the groundwork for future PRs that will introduce Hypothesis strategies for PSBT and QR decode testing.

Screenshots

N/A No UI changes


This pull request is categorized as a:

  • New feature
  • Bug fix
  • Code refactor
  • Documentation
  • Other

Checklist

I ran pytest locally

  • All tests passed before submitting the PR
  • I couldn't run the tests
  • N/A

I included screenshots of any new or modified screens

Should be part of the PR description above.

  • Yes
  • No
  • N/A

I added or updated tests

Any new or altered functionality should be covered in a unit test. Any new or updated sequences require FlowTests.

  • Yes
  • No, I’m a fool
  • N/A

I tested this PR hands-on on the following platform(s):


I have reviewed these notes:

  • Keep your changes limited in scope.
  • If you uncover other issues or improvements along the way, ideally submit those as a separate PR.
  • The more complicated the PR, the harder it is to review, test, and merge.
  • We appreciate your efforts, but we're a small team of volunteers so PR review can be a very slow process.
  • Please only "@" mention a contributor if their input is truly needed to enable further progress.
  • I understand

Thank you! Please join our Devs' Telegram group to get more involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant