Fixup

.github/workflows/ci-workflow.yml

@@ -158,8 +158,8 @@ jobs:
 
       - name: Run tests
         run: |
-          cd tests_mainnet
           pip install -r requirements.txt
+          cd tests_mainnet
           PYTHONPATH=$PYTHONPATH:/speculos pytest --headless --model=${{ matrix.model }} --timeout=300
 
   job_test_python_lib_legacyapp:
@@ -184,8 +184,8 @@ jobs:
 
       - name: Run tests
         run: |
-          cd bitcoin_client/tests
           pip install -r requirements.txt
+          cd bitcoin_client/tests
           PYTHONPATH=$PYTHONPATH:/speculos pytest --headless --timeout=300 --model=nanos
 
   job_perftests:
@@ -217,8 +217,8 @@ jobs:
 
       - name: Run tests
         run: |
-          cd tests_perf
           pip install -r requirements.txt
+          cd tests_perf
           PYTHONPATH=$PYTHONPATH:/speculos pytest --headless --model=nanosp --benchmark-json=benchmarks.json
       - name: Upload benchmarks summary
         uses: actions/upload-artifact@v4

bitcoin_client/tests/requirements.txt → requirements.txt

@@ -1,10 +1,13 @@
-bip32>=3.4,<4.0
+# requirements for the various test suites
+
+pytest>=6.1.1,<7.0.0
+pytest-timeout>=2.1.0,<3.0.0
 ledgercomm>=1.1.0,<1.2.0
 ecdsa>=0.16.1,<0.17.0
+typing-extensions>=3.7,<4.0
 embit>=0.7.0,<0.8.0
 mnemonic==0.20
-pytest>=6.1.1,<7.0.0
-pytest-timeout>=2.1.0,<3.0.0
+bip32>=3.4,<4.0
 speculos>=0.12.0,<0.13.0
-typing-extensions>=3.7,<4.0
--e ../
+ragger[speculos, ledgerwallet]>=1.6.0
+-e ./bitcoin_client  # path relative to the current working directory; assume it's the root of the repo

tests/requirements.txt

@@ -1,11 +1,3 @@
-pytest>=6.1.1,<7.0.0
-pytest-timeout>=2.1.0,<3.0.0
-ledgercomm>=1.1.0,<1.2.0
-ecdsa>=0.16.1,<0.17.0
-typing-extensions>=3.7,<4.0
-embit>=0.7.0,<0.8.0
-mnemonic==0.20
-bip32>=3.4,<4.0
-speculos>=0.12.0,<0.13.0
--e ../bitcoin_client
-ragger[speculos, ledgerwallet]>=1.6.0
+# The reusable ragger workflow expects a requirements.txt file in the tests directory, but we want to just use the one in the repository's root.
+# This works because the `pip install command` in the workflow is run from the repo's root.
+-r ./requirements.txt