We need to add test cases for all classes within the qbraid.runtime.ionq module.
To develop these tests, I highly recommend getting an IonQ access key so you can run actual jobs. You can do so simply by making an account at: https://ionq.com/quantum-cloud. Submitting jobs to their simulator device is free.
If you would rather not make an account, it would be possible to write these tests just using the IonQ API reference: https://docs.ionq.com/api-reference/v0.3/introduction.
Regardless of your approach, before merging, we will want these test cases to be runnable without an IonQ access key. The easiest way to achieve this is to use unittest.mock to replicate the responses from the IonQ server.
We need to add test cases for all classes within the qbraid.runtime.ionq module.
To develop these tests, I highly recommend getting an IonQ access key so you can run actual jobs. You can do so simply by making an account at: https://ionq.com/quantum-cloud. Submitting jobs to their
simulatordevice is free.If you would rather not make an account, it would be possible to write these tests just using the IonQ API reference: https://docs.ionq.com/api-reference/v0.3/introduction.
Regardless of your approach, before merging, we will want these test cases to be runnable without an IonQ access key. The easiest way to achieve this is to use unittest.mock to replicate the responses from the IonQ server.