test(e2e): CT-Automation MVP flow fails initial unavailable-state assertion #390

Open
opened 2026-06-02 07:41:04 +00:00 by simon · 0 comments
Owner

During a full local pnpm test:e2e run from apps/web, after fixing the auth E2E failures, the suite still exposed a separate failure in tests/e2e/automation/ct-automation-mvp.spec.ts:\n\nCT-Automation MVP flow covers connection health, job creation, launch, live log, and final summary failed at the initial jobs-page unavailable-state assertion. Playwright waited for getByTestId('ct-automation-jobs-unavailable') to contain disabled, but the element was not found within the 10s expect timeout.\n\nEvidence from the run:\n- Command: pnpm test:e2e in apps/web\n- Failure: expect(page.getByTestId('ct-automation-jobs-unavailable')).toContainText('disabled')\n- Nearby test setup seeds an eligible host group, visits /automation/jobs, expects ct-automation-create-job disabled, switches to the connection tab, then expects the unavailable alert.\n\nThis appears separate from the auth E2E fixture/timing issues fixed in the current branch. The CT-Automation test should either explicitly seed the disabled feature/connection precondition it expects or update the assertion to match the current jobs shell state.

During a full local `pnpm test:e2e` run from apps/web, after fixing the auth E2E failures, the suite still exposed a separate failure in `tests/e2e/automation/ct-automation-mvp.spec.ts`:\n\n`CT-Automation MVP flow covers connection health, job creation, launch, live log, and final summary` failed at the initial jobs-page unavailable-state assertion. Playwright waited for `getByTestId('ct-automation-jobs-unavailable')` to contain `disabled`, but the element was not found within the 10s expect timeout.\n\nEvidence from the run:\n- Command: `pnpm test:e2e` in `apps/web`\n- Failure: `expect(page.getByTestId('ct-automation-jobs-unavailable')).toContainText('disabled')`\n- Nearby test setup seeds an eligible host group, visits `/automation/jobs`, expects `ct-automation-create-job` disabled, switches to the connection tab, then expects the unavailable alert.\n\nThis appears separate from the auth E2E fixture/timing issues fixed in the current branch. The CT-Automation test should either explicitly seed the disabled feature/connection precondition it expects or update the assertion to match the current jobs shell state.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carrtech/ct-ops#390
No description provided.