Add qiskit-neko integration tests #162
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pull Request Test Coverage Report for Build 8019925179Details
💛 - Coveralls |
woodsp-ibm
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Since Qiskit/qiskit-neko#34, the
qiskit-nekonature and primitives tests useqiskit_algorithms.This PR adds a new CI job to run the neko integration tests to (double) check that a proposed PR does not regress compatibility on an API or an integration point with another qiskit project and ensure that algorithms doesn't break CI for another project using neko.
Details and comments
Gap discovered in Qiskit/qiskit-neko#41.
I've added two jobs, one for the nature tests and one for the primitives tests because I didn't find a way to squeeze both options into one job. Feel free to suggest how to do it if you have a better alternative.--> The better alternative is using the new component added in Qiskit/qiskit-neko#43.