fix(workbench): skip disabled resource profiles in capacity test

[samcofer]

What

Fixes the test_launch_sessions_with_the_configured_resource_profile[chromium] timeout when a Workbench resource profile is visible but disabled for the authenticated user.

Closes #514

Root cause

Workbench renders resource profiles a user is not entitled to (e.g. a group-restricted profile) as visible [role='option'] elements marked aria-disabled="true" / data-disabled. The capacity test detected every option as launchable, then option.click() on a disabled one blocked until Playwright's 5s timeout:

locator resolved to <div role="option" data-disabled="" aria-disabled="true" ...>
  - element is not enabled - retrying click action
TimeoutError: Locator.click: Timeout 5000ms exceeded.

Fix

• _option_is_disabled() — new helper checking aria-disabled / data-disabled.
• _detect_profiles() — now returns each profile's name and disabled flag (instead of a bare name list).
• Auto-detect (launch_sessions) — launches only enabled profiles; skips the whole scenario with a clear reason only when every profile is disabled (nothing launchable).
• _launch_session() — checks the resolved option before clicking and raises ResourceProfileDisabled rather than clicking a disabled option. An explicitly configured (workbench.session_profiles) but disabled profile now pytest.skips with a message naming the profile and the likely group/entitlement restriction.

Behavior decisions

Case	Behavior
Configured profile disabled for user	pytest.skip with reason (environment condition, not a failure)
Auto-detected, some disabled	filter out disabled, launch the rest
Auto-detected, all disabled	pytest.skip — nothing launchable

Testing

• ruff check / ruff format --check pass.
• pytest --collect-only collects cleanly.
• Product test — cannot run in CI (no Workbench deployment).

🤖 Generated with Claude Code

[ian-flores]

Hey Sam. I reviewed #515 and pushed one commit onto your branch (681d2152).

Three things it changes:

• launch_sessions was bailing on the whole scenario the moment it hit one disabled configured profile. Now it skips just that profile, keeps launching the rest, and only skips the scenario if nothing was launchable.
• test_session_capacity_k8s.py had its own copy of _launch_session that still clicked disabled options and hung. I pulled _option_is_disabled and ResourceProfileDisabled into conftest.py and wired the check into the k8s file too.
• The list[dict[str, object]] profile records are now a DetectedProfile frozen dataclass, which drops the str() casts.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-07-22 19:01 UTC