forked from HAL9000/cleveragents-core
freemo
8ea00f5185
Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>
30 lines
1.7 KiB
Gherkin
30 lines
1.7 KiB
Gherkin
@tdd_issue @tdd_issue_592 @tdd_issue_4176
|
|
Feature: TDD Issue #592 — actor list validation rejects multi-slash model names
|
|
As a developer
|
|
I want to verify that `agents actor list` raises a validation error when
|
|
a provider has a model name containing `/` separators
|
|
So that the bug is captured and will be caught by a regression test
|
|
|
|
The root cause is that `ActorRegistry._actor_name()` builds actor names
|
|
via `f"{provider}/{model}"`. When a provider's default model already
|
|
contains `/` (e.g. `anthropic/claude-sonnet-4-20250514`), the resulting
|
|
name has 2+ slashes and `ActorService._normalize_name()` rejects it with
|
|
`ValidationError("Actor names must include exactly one '/' separator")`.
|
|
|
|
Scenario: Actor list with multi-slash model does not raise validation error
|
|
Given an actor registry with a multi-slash model provider for tdd-actor-validation
|
|
When I run actor list via the tdd-actor-validation CLI
|
|
Then the tdd-actor-validation exit code should be 0
|
|
And the tdd-actor-validation output should not contain "VALIDATION_FAILED"
|
|
|
|
Scenario: Built-in actor names have exactly one slash separator
|
|
Given an actor registry with a multi-slash model provider for tdd-actor-validation
|
|
When I run actor list via the tdd-actor-validation CLI
|
|
Then the tdd-actor-validation upserted actor name should contain exactly one slash
|
|
|
|
Scenario: Actor list JSON format with multi-slash model succeeds
|
|
Given an actor registry with a multi-slash model provider for tdd-actor-validation
|
|
When I run actor list with format json via the tdd-actor-validation CLI
|
|
Then the tdd-actor-validation exit code should be 0
|
|
And the tdd-actor-validation output should be valid JSON
|