fix(tests): restore 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). run_autorun_job validates job names before reading status, so the test never reached the list/dict status parsing logic it was meant to exercise.

Changes

• Update test_run_autorun_job_reads_status_for_list_and_dict_shapes to use the whitelisted smoke job name in parametrized payloads and assertions.

Verification

• pytest tests/test_quantum_integration.py — 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

  All steps passed:
  • repair_data_out_status (12 files scanned, 0 repaired)
  • pre_commit_check (2728 tests passed)
  • integration_contract_gate
  • run_repo_agents (status-freshness ok; docstring/marker warnings expected)

Co-authored-by: Bryan bryan@users.noreply.github.com

  

Summary by Sourcery

Tests:

• Adjust quantum integration test payloads and assertions to use the whitelisted 'smoke' job and restore coverage of list/dict status parsing.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the quantum integration autorun test to use a whitelisted job name so it exercises the intended status parsing paths without failing earlier job-name validation.

File-Level Changes

Change	Details	Files
Align autorun integration test with whitelisted job name validation so status parsing for list/dict shapes is actually exercised.	Update parametrized jobs_payload fixtures to use the whitelisted 'smoke' job key/name instead of 'another' for both list and dict payload shapes Change the run_autorun_job invocation to pass 'smoke' as the job name so it passes validation and reaches status parsing logic Adjust assertions on result['job_name'] and result['status']['name'] to expect 'smoke' while keeping preset/status shape checks intact	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 — 2391c41

Metric	Value
Total coverage	65.3%
▲ vs main	+0.1%
Minimum threshold	60%

Updated on every push · 2026-06-20