Skip to content

fix(tests): repair quantum integration test for allowed job names#460

Merged
Bryan-Roe merged 1 commit into
mainfrom
cursor/repository-automation-9941
Jun 21, 2026
Merged

fix(tests): repair quantum integration test for allowed job names#460
Bryan-Roe merged 1 commit into
mainfrom
cursor/repository-automation-9941

Conversation

@cursor

@cursor cursor Bot commented Jun 20, 2026

Copy link
Copy Markdown

Summary

Hourly repo health automation failed on two quantum integration tests. The tests called run_autorun_job("another"), but the API only accepts whitelisted job names (baseline, benchmark, nightly, smoke).

Changes

  • Updated tests/test_quantum_integration.py to use the allowed smoke job name in both list- and dict-shaped status payload cases
  • Preserves coverage of _find_job_status normalization through the public run_autorun_job API

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, pre-commit, integration gate, repo agents)
  • Unit suite: 2725 passed, 50 skipped

Co-authored-by: Bryan

Open in Web View Automation 

Summary by Sourcery

Tests:

  • Adjust quantum integration tests to validate list- and dict-shaped job status payloads using the whitelisted 'smoke' job name.

Note

Low Risk
Test-only rename with no production code changes.

Overview
Repairs failing quantum integration tests by aligning fixture job names with run_autorun_job’s allowed set (baseline, benchmark, nightly, smoke).

Parameterized list- and dict-shaped status.json payloads and assertions now use smoke instead of another, so the tests still exercise status lookup without tripping the invalid job name guard.

Reviewed by Cursor Bugbot for commit 7a73b1c. Bugbot is set up for automated code reviews on this repo. Configure here.

The run_autorun_job whitelist rejects arbitrary names like 'another';
update the list/dict status-shape test to use 'smoke' so it exercises
_find_job_status through the public API.

Co-authored-by: Bryan
@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 the quantum integration test to use an allowed autorun job name ('smoke') instead of a disallowed value, keeping coverage of list/dict job status payload handling and the run_autorun_job contract intact.

File-Level Changes

Change Details Files
Align quantum integration test fixtures and expectations with the allowed 'smoke' autorun job name while preserving list/dict status payload coverage.
  • Update parametrized jobs_payload fixtures to use job name 'smoke' for both list- and dict-shaped payloads
  • Adjust run_autorun_job invocation to request the 'smoke' job instead of the previously used disallowed name
  • Update assertions on result['job_name'] and result['status']['name'] to match the 'smoke' job name, ensuring behavior is validated end-to-end
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 — f9a6ee2

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

Updated on every push · 2026-06-20

@Bryan-Roe Bryan-Roe marked this pull request as ready for review June 21, 2026 06:40
@Bryan-Roe Bryan-Roe self-requested a review as a code owner June 21, 2026 06:40
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@Bryan-Roe Bryan-Roe merged commit 24dd036 into main Jun 21, 2026
45 of 71 checks passed
@Bryan-Roe Bryan-Roe deleted the cursor/repository-automation-9941 branch June 21, 2026 06:40

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

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.

2 participants