Skip to content

[PLT-0] Skip test_labeling_frontend_connecting_to_project (removed capability)#2066

Merged
mrobers1982 merged 1 commit into
developfrom
mrobers1982/skip-legacy-labeling-frontend-test
Jul 13, 2026
Merged

[PLT-0] Skip test_labeling_frontend_connecting_to_project (removed capability)#2066
mrobers1982 merged 1 commit into
developfrom
mrobers1982/skip-legacy-labeling-frontend-test

Conversation

@mrobers1982

@mrobers1982 mrobers1982 commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Summary

test_labeling_frontend_connecting_to_project has been failing on all 5 Python versions in the develop integration suite. The root cause is a removed backend capability, not a stale assertion.

Per intelligence #30098 ("Remove legacy custom and DICOM editors"), the backend's getEditorType now only accepts modern Pictor editor URLs. Projects auto-attach the correct frontend, and a manual project.labeling_frontend.connect(<legacy "Editor" frontend>) is now rejected with MalformedQueryException: Unsupported labeling frontend. The test fails at the connect() call before reaching any later assertions.

This is the only remaining deterministic (non-environmental) code failure from the develop CI cleanup effort.

Changes

  • Add an unconditional @pytest.mark.skip to test_labeling_frontend_connecting_to_project in libs/labelbox/tests/integration/test_labeling_frontend.py, with a reason= citing intelligence #30098.
  • Test body left unchanged so the change is fully reversible if the capability returns or the test is rewritten against a supported Pictor frontend.
  • test_get_labeling_frontends is untouched.

Skip vs. delete: skipping (rather than deleting) keeps the code in place and documents why inline, pending a separate follow-up on whether the SDK connect/disconnect methods should be deprecated or rewritten against a modern Pictor frontend.

Test Plan

Verified locally:

  • test_labeling_frontend_connecting_to_project reports SKIPPED with the reason (no live backend needed).
  • Both tests still collect (--collect-only → 2 items); test_get_labeling_frontends unaffected.
  • ruff 0.8.2 check and format --check pass (matching CI's bundled ruff).

CI will confirm the test is skipped across all Python versions.

🤖 Generated with Claude Code


Note

Low Risk
Test-only change with no production code or runtime behavior impact.

Overview
Marks test_labeling_frontend_connecting_to_project as skipped so the develop integration suite stops failing on a removed backend behavior.

The test manually connects the legacy "Editor" frontend via project.labeling_frontend.connect(), which the API now rejects (MalformedQueryException: Unsupported labeling frontend) after intelligence #30098—only modern Pictor editors are accepted and projects auto-attach the right frontend. The skip reason documents that in-line; the test body is unchanged for a possible future rewrite against a supported frontend. test_get_labeling_frontends is unchanged.

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

…pability)

Manual connect() of the legacy 'Editor' labeling frontend is no longer
supported: per intelligence #30098 the backend's getEditorType only
accepts modern Pictor editors, so connecting the legacy frontend now
returns MalformedQueryException. Projects auto-attach the correct
frontend. Skip (rather than delete) keeps the test in place and
reversible pending a follow-up on whether connect/disconnect should be
deprecated or rewritten against a supported Pictor frontend.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mrobers1982
mrobers1982 merged commit 6a9a8e3 into develop Jul 13, 2026
16 of 26 checks passed
@mrobers1982
mrobers1982 deleted the mrobers1982/skip-legacy-labeling-frontend-test branch July 13, 2026 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants