fix(tests): use whitelisted smoke job in quantum integration test

[cursor]

Summary

Hourly repo health automation failed on pre_commit_check because tests/test_quantum_integration.py used a non-whitelisted autorun job name (another). The quantum integration bridge validates job names before status lookup, so the parametrized fixtures never reached the list/dict status parsing logic they were meant to exercise.

Changes

• Updated parametrized fixtures to use the whitelisted smoke job name instead of another
• Assertions now expect smoke in job name and status payload fields

Verification

• pytest tests/test_quantum_integration.py -q — 2 passed
• Full health cycle: PYTHON_BIN=.venv/bin/python .venv/bin/python scripts/repo_health_automation.py --once --repair-status --refresh-stale-status --run-agents --continue-on-fail
  • repair_data_out_status: PASS
  • pre_commit_check: PASS (2725 tests)
  • integration_contract_gate: PASS
  • run_repo_agents: PASS (status-freshness ok; docstring/marker warnings expected)

  

Summary by Sourcery

Tests:

• Update quantum integration test fixtures and assertions to use the whitelisted 'smoke' job name instead of a non-whitelisted value.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the quantum integration test to use the whitelisted smoke autorun job so the test exercises list/dict status parsing instead of failing on job-name validation, and aligns all expectations with the new job name.

File-Level Changes

Change	Details	Files
Parametrized quantum integration test fixtures now use the whitelisted smoke job instead of a non-whitelisted job name and assertions are updated accordingly.	Changed parametrized jobs_payload cases to use a job object keyed and named smoke instead of another while keeping the preset and status fields the same. Updated the run_autorun_job invocation to pass smoke as the job name so it passes bridge validation. Adjusted assertions to expect smoke for job_name and status.name while still validating the preset and dry_run behavior.	tests/test_quantum_integration.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

🟡 Coverage — 77954b4

Metric	Value
Total coverage	65.2%
→ vs main	0.0%
Minimum threshold	60%

Updated on every push · 2026-06-20