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 the non-whitelisted job name another. The quantum integration bridge only accepts baseline, benchmark, nightly, and smoke, so the test never reached status lookup logic.

Changes

• Updated test_run_autorun_job_reads_status_for_list_and_dict_shapes to use the whitelisted smoke job name in fixtures and assertions.

Verification

• pytest tests/test_quantum_integration.py -v — 2 passed
• Full health cycle: PYTHON_BIN=.venv/bin/python scripts/repo_health_automation.py --once --repair-status --refresh-stale-status --run-agents --continue-on-fail — all steps passed (2725 unit tests, integration contract gate, repo agents)

Checklist

• I added or updated tests for new behavior
• I updated relevant documentation (README, .github/copilot-instructions.md, instruction files)
• All unit tests pass locally (python scripts/test_runner.py --unit)
• No hardcoded secrets or API keys introduced
• PR title clearly describes the change (not a generic codespace/branch name)

  

Summary by Sourcery

Bug Fixes:

• Update quantum integration autorun job test to use the supported 'smoke' job name instead of a non-whitelisted job, ensuring the test passes and validates status handling.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts the quantum integration test to use a whitelisted job name ('smoke') so the autorun job status lookup logic is exercised correctly for both list and dict job payload shapes.

File-Level Changes

Change	Details	Files
Update quantum integration autorun job test fixtures and assertions to use the whitelisted 'smoke' job name instead of the non-whitelisted 'another'.	Change parametrized jobs_payload fixtures to use 'smoke' as the job name in both list and dict payload shapes while keeping preset/status the same. Update the call to integration.run_autorun_job to pass 'smoke' as the job name so the bridge accepts and processes the job. Adjust assertions to expect 'smoke' for job_name and status.name while still validating preset and status structure.	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 — 7b3a876

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

Updated on every push · 2026-06-20