28 lines
1.3 KiB
Gherkin
28 lines
1.3 KiB
Gherkin
@tdd_issue @tdd_issue_570 @tdd_issue_4178
|
|
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
|
|
|
|
@tdd_issue @tdd_issue_4368
|
|
Scenario: Session create command produces structured output via DI
|
|
Given a CLI runner using the real session DI path
|
|
When I invoke session create with actor "local/orchestrator" and format "json"
|
|
Then the session create command should exit successfully
|
|
And the session create JSON response should match the session create spec
|