-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop the TorchQuantum Testing Suite #261
Develop the TorchQuantum Testing Suite #261
Comments
Hey, For example, the files in - name: Unit Tests
- env:
IBM_API_TOKEN: ${{ secrets.IBM_API_TOKEN }}
run: |
python -m pytest tests And, any file that defines the 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 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? |
Currently, TQ’s tests don’t quite have full coverage, and we need your helps to achieve near-full coverage! To take on this task, take a module which has limited or lacking tests (found in
test/
) and write a comprehensive testing set for it! Some places that still need tests include the encoders, the operators (with different params likeinverse=True
), and covering all of the measurements!Another super helpful directions we would love help with is we want to automatically run ALL of our tests using GitHub actions, but we don’t yet have a method to authenticate through IBMQ via GitHub actions. If you can design a workflow that can run the
test/plugin
tests on GitHub actions, that would super helpful!The task will be considered complete if you develop a rigorous testing suite for at least two different components (and one of those tqo can be adding IBMQ support on GH actions).
The text was updated successfully, but these errors were encountered: