forked from HAL9000/cleveragents-core
hurui200320
1878998b7a
Rename the TDD tag system from tdd_bug/tdd_bug_<N> to tdd_issue/tdd_issue_<N> across the entire codebase. The tdd_expected_fail tag is unchanged. The TDD expected-failure workflow is not limited to bug fixes — it applies equally to any issue type (features, tasks, refactors). The _bug suffix was misleading and narrowed the perceived scope. The new _issue suffix accurately reflects that the TDD tagging system applies to any Forgejo issue. Changes span 92 files: - features/environment.py: validate_tdd_tags(), should_invert_result(), and apply_tdd_inversion() updated — regex, variables, error messages - robot/tdd_expected_fail_listener.py: _validate_tdd_tags(), _should_invert_result(), start_test(), end_test() updated consistently - 33 Behave .feature files: all @tdd_bug/@tdd_bug_<N> tags renamed - 29 Robot .robot files: all tdd_bug/tdd_bug_<N> tags renamed - 3 Robot fixture files renamed (tdd_bug_alone, tdd_missing_tdd_bug, tdd_expected_fail_missing_bug_n) with content and references updated - Tag validation tests and helpers updated (function names, command dispatch keys, output strings, fixture references) - CONTRIBUTING.md: section renamed from 'TDD Bug Test Tags' to 'TDD Issue Test Tags', all tag references and examples updated - noxfile.py: comment references updated - Step definition files, mock helpers, and benchmark files: docstring references updated ISSUES CLOSED: #965
30 lines
1.7 KiB
Gherkin
30 lines
1.7 KiB
Gherkin
@tdd_issue @tdd_issue_592
|
|
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
|