[INFO] ELITEA-1739 test data uses skill names invalid under the live Name-field slug constraint
Found while working #127 (ELITEA-1739 "Search Skills by Name" test-case analysis)
Environment: https://next.elitea.ai/app/skills/create, Chromium, account alita@elitea.ai
Observation: ELITEA-1739's Test Data table specifies skill names "Formatter", "Code Reviewer", "Content Writer" — mixed case, with spaces. The live Skill creation form's "Name" field rejects this: live validation message is "Name must be lowercase letters, digits and hyphens only (no spaces), and cannot start or end with a hyphen." Confirmed by typing "Formatter" into the Name field and observing the [invalid] state + that exact message; "formatter" (lowercase, no space) was accepted.
Impact: This is case-text drift, not a product defect — the live product's constraint is a reasonable, intentional naming rule (Skills are presumably referenced as slugs elsewhere, e.g. in agent configuration). The case's search-by-name intent (partial/exact/non-existent/clear) is unaffected; only the literal example names need updating.
Suggested correction to the case text: replace the three names with slug-valid equivalents, e.g. formatter, code-reviewer, content-writer, and adjust the "partial search term" example accordingly (see #128 for why "Co" specifically doesn't work either, for an unrelated reason — a 3-character search minimum).
Action requested: whoever owns ELITEA-1739's case text in EliteaAI/onetest-ai-tm-Elitea should update the Test Data table to slug-valid names. No code/product change needed.
[INFO] ELITEA-1739 test data uses skill names invalid under the live Name-field slug constraint
Found while working #127 (ELITEA-1739 "Search Skills by Name" test-case analysis)
Environment:
https://next.elitea.ai/app/skills/create, Chromium, accountalita@elitea.aiObservation: ELITEA-1739's Test Data table specifies skill names "Formatter", "Code Reviewer", "Content Writer" — mixed case, with spaces. The live Skill creation form's "Name" field rejects this: live validation message is "Name must be lowercase letters, digits and hyphens only (no spaces), and cannot start or end with a hyphen." Confirmed by typing "Formatter" into the Name field and observing the
[invalid]state + that exact message; "formatter" (lowercase, no space) was accepted.Impact: This is case-text drift, not a product defect — the live product's constraint is a reasonable, intentional naming rule (Skills are presumably referenced as slugs elsewhere, e.g. in agent configuration). The case's search-by-name intent (partial/exact/non-existent/clear) is unaffected; only the literal example names need updating.
Suggested correction to the case text: replace the three names with slug-valid equivalents, e.g.
formatter,code-reviewer,content-writer, and adjust the "partial search term" example accordingly (see #128 for why "Co" specifically doesn't work either, for an unrelated reason — a 3-character search minimum).Action requested: whoever owns ELITEA-1739's case text in
EliteaAI/onetest-ai-tm-Eliteashould update the Test Data table to slug-valid names. No code/product change needed.