Skip to content

test(ui): cover agent creation form validation - #3017

Open
chipfighter wants to merge 3 commits into
kagent-dev:mainfrom
chipfighter:test/agent-form-validation
Open

chipfighter wants to merge 3 commits into
kagent-dev:mainfrom
chipfighter:test/agent-form-validation

Conversation

@chipfighter

@chipfighter chipfighter commented Sep 30, 2026 •

Copy link
Copy Markdown

Summary

Cover creation-form validation in the existing Agent CRUD journeys for referenced and inline templates, both using a referenced harness:

  • Required field markers and disabled submission on an empty form.
  • Feedback for a missing name, template, inline model configuration, and harness.
  • Cleared validation feedback and enabled submission once the form is complete.

Reuse the shared required-field helper and preserve the current two CRUD cases and chat-entry coverage. The change is limited to ui/playwright/tests/agents/agent-crud.spec.ts (+20/-2) against main at 73e540a.

Validation

  • yarn install --immutable — passed.
  • yarn typecheck — passed.
  • yarn lint — 0 errors; 6 existing warnings in unrelated files.
  • yarn test:pw playwright/tests/agents/agent-crud.spec.ts --project=chromium --project=firefox --workers=2 — all 4 tests passed on Windows.
  • git diff --check — passed.

Signed-off-by: chipfighter <92256151+chipfighter@users.noreply.github.com>
@github-actions github-actions Bot added the testing Additional testing required label Sep 30, 2026
Charlesthebird
Charlesthebird previously approved these changes Oct 1, 2026
Signed-off-by: chipfighter <92256151+chipfighter@users.noreply.github.com>
@github-actions github-actions Bot added testing Additional testing required and removed testing Additional testing required labels Oct 10, 2026
@chipfighter

Copy link
Copy Markdown
Author

I synchronized this branch with main, preserving its four CRUD cases and chat-entry simplification. The PR still changes only the creation-validation assertions (+26/-2). Local verification passed: typecheck, lint (0 errors; 6 existing warnings), and all 8 CRUD cases across Chromium and Firefox.

The approval and auto-merge setting are still present. The latest CI Build run is awaiting approval to run. Could you approve it and add the PR to the merge queue after the required checks pass?

@Charlesthebird

Copy link
Copy Markdown
Collaborator

This has some merge conflicts

await expect(submit).toBeDisabled();
await expect(problems).toHaveText("Choose a harness.");
if (harness === "inline") {
await chooseSource(page, "harness", "inline");

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.

inline harness is gone on main, does this run?

Signed-off-by: chipfighter <92256151+chipfighter@users.noreply.github.com>
@github-actions github-actions Bot added testing Additional testing required and removed testing Additional testing required labels Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

testing Additional testing required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants