Skip to content

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

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/repository-automation-2573
Draft

fix(tests): use whitelisted smoke job name in quantum integration test#467
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/repository-automation-2573

Conversation

@cursor

@cursor cursor Bot commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Hourly repo health automation failed because tests/test_quantum_integration.py used a non-whitelisted autorun job name (another). QuantumIntegration.run_autorun_job validates against allowed names before reading status payloads.

Changes

  • Update parametrized fixtures and assertions to use the whitelisted smoke job name.

Verification

  • pytest tests/test_quantum_integration.py — 2 passed
  • PYTHON_BIN=.venv/bin/python scripts/repo_health_automation.py --once --repair-status --refresh-stale-status --run-agents --continue-on-fail — all steps passed (repair, pre-commit, integration gate, repo agents)
Open in Web View Automation 

Summary by Sourcery

Tests:

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

run_autorun_job rejects non-whitelisted names before status lookup;
align parametrized fixtures with allowed job_name values.

Co-authored-by: Bryan <bryan@users.noreply.github.com>
@sourcery-ai

sourcery-ai Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates quantum integration tests to use the whitelisted 'smoke' autorun job name so they align with QuantumIntegration.run_autorun_job validation and repo health automation expectations.

File-Level Changes

Change Details Files
Align quantum integration autorun job tests with allowed 'smoke' job name validation.
  • Update parametrized job payload fixtures from the non-whitelisted 'another' job name to the whitelisted 'smoke' job name for both list and dict payload shapes.
  • Adjust test invocation of run_autorun_job to request the 'smoke' job instead of 'another'.
  • Update assertions on returned job_name and status.name fields to expect 'smoke'.
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

@github-actions github-actions Bot added the tests label Jun 20, 2026
@github-actions

Copy link
Copy Markdown

🟡 Coverage — 866287d

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

Updated on every push · 2026-06-20

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant