-
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
Conversation
Co-authored-by: toolate28 <105518313+toolate28@users.noreply.github.com>
57c68d6 to
6308455
Compare
|
🌀 Agent Review: Coherence >60%. Ethical quantum sims validated. Ready for merge. |
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.
Pull request overview
This PR adds comprehensive test coverage for the qubit range validation security feature that prevents resource exhaustion attacks by limiting qubit indices to 0-100. The implementation code already exists in agent_skills.py, and these tests ensure it works correctly across various scenarios.
Changes:
- Added TestQubitRangeValidation class with 21 tests covering boundary conditions, single-qubit gates, two-qubit gates, and error message formats
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| expected_msg = "Qubit index 150 out of range. Must be between 0 and 100." | ||
| assert result['error'] == expected_msg | ||
|
|
||
| def test_error_message_format_cx_control(self): | ||
| """Test error message format for CX gate with invalid control""" | ||
| result = agent_skills.simulate_circuit("cx(150,0)") | ||
| assert result['status'] == 'error' | ||
| expected_msg = "Control qubit index 150 out of range. Must be between 0 and 100." | ||
| assert result['error'] == expected_msg | ||
|
|
||
| def test_error_message_format_cx_target(self): | ||
| """Test error message format for CX gate with invalid target""" | ||
| result = agent_skills.simulate_circuit("cx(0,150)") | ||
| assert result['status'] == 'error' | ||
| expected_msg = "Target qubit index 150 out of range. Must be between 0 and 100." | ||
| assert result['error'] == expected_msg |
Copilot
AI
Jan 18, 2026
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.
| expected_msg = "Qubit index 150 out of range. Must be between 0 and 100." | |
| assert result['error'] == expected_msg | |
| def test_error_message_format_cx_control(self): | |
| """Test error message format for CX gate with invalid control""" | |
| result = agent_skills.simulate_circuit("cx(150,0)") | |
| assert result['status'] == 'error' | |
| expected_msg = "Control qubit index 150 out of range. Must be between 0 and 100." | |
| assert result['error'] == expected_msg | |
| def test_error_message_format_cx_target(self): | |
| """Test error message format for CX gate with invalid target""" | |
| result = agent_skills.simulate_circuit("cx(0,150)") | |
| assert result['status'] == 'error' | |
| expected_msg = "Target qubit index 150 out of range. Must be between 0 and 100." | |
| assert result['error'] == expected_msg | |
| error_msg = result.get('error', '') | |
| assert 'out of range' in error_msg.lower() | |
| assert '150' in error_msg | |
| def test_error_message_format_cx_control(self): | |
| """Test error message format for CX gate with invalid control""" | |
| result = agent_skills.simulate_circuit("cx(150,0)") | |
| assert result['status'] == 'error' | |
| error_msg = result.get('error', '') | |
| assert 'out of range' in error_msg.lower() | |
| assert '150' in error_msg | |
| def test_error_message_format_cx_target(self): | |
| """Test error message format for CX gate with invalid target""" | |
| result = agent_skills.simulate_circuit("cx(0,150)") | |
| assert result['status'] == 'error' | |
| error_msg = result.get('error', '') | |
| assert 'out of range' in error_msg.lower() | |
| assert '150' in error_msg |
|
@copilot apply changes based on the comments in this thread |
The qubit range validation feature (MAX_QUBIT_INDEX=100) added to prevent resource exhaustion attacks had no test coverage.
Changes
Added
TestQubitRangeValidationclass with 21 tests covering:Fixed missing
Unionimport inagent_skills.pytype hintsExample
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.