-
Notifications
You must be signed in to change notification settings - Fork 10
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
[WIP] Refactor plugin template #1
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, and much more flexible, thanks @johannesjmeyer!
I just noticed that it is still WIP; let me know when it is review ready and I'll look over any additional changes. |
Any plans to merge this PR @josh146 ? |
Oh, that would have probably been useful for my new plug-in 😅 But I think we should actually have a way to integration test plugins with code inside pennylane that is kept up to date at all times (it's always hard to keep all the plugins and the template up to date). Maybe we could have a functionality to integration test a plug-in with default.qubit as the normal?
I.e. something useable as
```
@pytest.mark.parametrize(*qml.test.parametrization("my device")
def test(args):
qml.test.case(args)
```
where test.case returns a sensible error message.
|
I agree. The tests in the plugin-template repo are pretty much useless if you want to make a device using Worth fixing the random mentions of qiskit/forest though 😆 |
This PR contains some minor refactoring in the plugin itself and some major changes that make the plugin template tests more flexible.