Skip to content

flake: e2e create workspace with default and required parameters #1154

@flake-investigator

Description

@flake-investigator

CI Run: https://github.com/coder/coder/actions/runs/19690006849
Commit: 9c2f94b574fc40d79d9abb0d23ef71b18a9d6b4f (Benjamin Cohen)
Job: test-e2e

Failure summary:

  • Playwright test failed: [tests] › e2e/tests/workspaces/createWorkspace.spec.ts:79:5 › create workspace with default and required parameters
  • Assertion mismatch in helpers.ts when verifying parameter input value

Error excerpt:

Error: expect(received).toEqual(expected) // deep equality

Expected: "12345"
Received: ""

at helpers.ts:211
  209 |     const parameterField = parameterLabel.locator("input");
  210 |     const value = await parameterField.inputValue();
> 211 |     expect(value).toEqual(buildParameter.value);
      |                   ^
  212 |   }
  213 |   break;
  214 |   default:
  at verifyParameters (site/e2e/helpers.ts:211:20)
  at site/e2e/tests/workspaces/createWorkspace.spec.ts:103:2

Timing verification:

  • Job completed at 2025-11-26T02:06:23Z (within minutes of Slack alert at 02:27Z).

Duplicate check:

  • Searched coder/internal for similar issues by test name and key error messages ("create workspace with default and required parameters", "verifyParameters", Playwright e2e) — none found.

Initial assessment:

  • Root cause classification: Flaky test or product change affecting default parameter handling.
  • Recent changes to parameters and e2e tests exist (e.g., removal of classic parameters frontend code). This failure suggests the test expects an initial value of "12345" but UI input is empty.

Assignment analysis:

  • Primary: test ownership. The failing spec lives at site/e2e/tests/workspaces/createWorkspace.spec.ts and helper at site/e2e/helpers.ts.
  • Recent meaningful changes to the spec file were by Kayla Washburn-Love. GitHub did not allow assigning automatically; leaving unassigned and tagging the area for triage.

Next steps requested:

  • Confirm whether the expected default parameter value still applies post-frontend changes.
  • If behavior change is intended, update the test expectations; otherwise, fix the UI logic and/or test setup that populates default/required parameters.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions