forked from cleveragents/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
27 lines
1.2 KiB
Gherkin
27 lines
1.2 KiB
Gherkin
@tdd_issue @tdd_issue_570
|
|
Feature: TDD Issue #570 — session create DI container missing db provider
|
|
As a developer
|
|
I want to verify that `agents session create` fails due to the
|
|
DI container missing a `db` provider
|
|
So that the bug is captured and will be caught by a regression test
|
|
|
|
The root cause is shared with bug #554: `_get_session_service()` in
|
|
session.py calls `container.db()`, but the Container class has no `db`
|
|
provider, causing an AttributeError at runtime.
|
|
|
|
Scenario: Session create command succeeds via DI container
|
|
Given a CLI runner using the real session DI path
|
|
When I invoke the session create command
|
|
Then the session create command should exit successfully
|
|
|
|
Scenario: Session create with actor succeeds via DI container
|
|
Given a CLI runner using the real session DI path
|
|
When I invoke the session create command with actor "openai/gpt-4"
|
|
Then the session create command should exit successfully
|
|
|
|
Scenario: Session create command produces structured output via DI
|
|
Given a CLI runner using the real session DI path
|
|
When I invoke the session create command with format json
|
|
Then the session create command should exit successfully
|
|
And the session create output should be valid JSON
|