Hey,
For the GitHub Actions issue, did you try saving an IBM API Token as a GitHub secret? GitHub secrets can be called from within the GitHub Actions workflow to run the tests.

For example, the files in tests/plugin require an IBM backend and consequently require an IBM token to initiate the IBMProvider. You could do something like this in the GitHub Actions workflow,

- name: Unit Tests
- env:
    IBM_API_TOKEN: ${{ secrets.IBM_API_TOKEN }}
run: |
    python -m pytest tests

And, any file that defines the IBMProvider or QiskitRuntimeSevice such as this can be written as,

import os
token = os.getenv("IBM_API_TOKEN")

provider = QiskitRuntimeService(channel = "ibm_quantum", token=token, instance = "ibm-q-research/mass-inst-tech-1/main")

The workflow will replace IBM_API_TOKEN with the saved token.

Correct me if I am wrong in understanding the situation. If this makes sense, I am glad to open a PR to see how this works out.

Update: I worked the above on a toy model and I was able to authenticate and schedule a job on the IBM Quantum platform.

Hey, thanks for letting us know! Feel free to open a PR with those updates (I can add in the secret with GH secrets as you recommended) + some tests for an aspect of your choosing, and we can merge it in!

Hey @GenericP3rson, just to confirm, does the testing suite require functional tests or unit tests?