generated from toolate28/spiralsafe-mono
-
Notifications
You must be signed in to change notification settings - Fork 0
Add test coverage for qubit range validation security feature #43
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
The exact error message assertions in these three tests make the tests brittle and tightly coupled to implementation details. Looking at the implementation in agent_skills.py, the _get_range_error_message function checks the control qubit first (line 211), then the target qubit (line 213). This means that when both qubits are out of range in a CX gate, only the control qubit error is reported.
However, test_error_message_format_cx_target (line 716) expects the exact error message for the target qubit, which will only occur if the control qubit is valid. If the logic in _get_range_error_message changes to check the target qubit first, or if it reports both errors, this test will fail even though the validation still works correctly.
Consider making these assertions more flexible by checking for key components (status, presence of out of range message, and the invalid index value) rather than exact string matching, similar to the approach used in the other tests in this class.