forked from cleveragents/cleveragents-core
d430d671a0
Extended `_print_actor()` to render the full spec-required output for `agents actor add`: the Actor Added panel now includes a Type field, and three additional panels (Config, Capabilities, Tools) plus a success status line are rendered when `show_add_panels=True`. - Add `Type:` field to the Actor Added panel (from `config_blob["type"]`) - Implement Config panel: Path, Hash, Options count, Nodes count, Edges count - Implement Capabilities panel: bulleted list (rendered only when non-empty) - Implement Tools panel: Rich table with Tool, Read-Only, Safe columns (rendered only when non-empty; string tool entries default to yes/yes) - Add `✓ OK Actor added` success status line after all panels - Pass `config_path` and `show_add_panels=True` from `add()` command - Add Behave BDD scenarios covering each new panel and the success line - Add Robot Framework integration test verifying the full rich output ISSUES CLOSED: #1499
50 lines
2.2 KiB
Gherkin
50 lines
2.2 KiB
Gherkin
Feature: actor add rich output panels
|
|
As a user of the CleverAgents CLI
|
|
I want `agents actor add` to display all spec-required panels
|
|
So that I can see the full details of a newly added actor
|
|
|
|
Scenario: Actor Added panel includes Type field
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the actor added panel should contain the Type field
|
|
|
|
Scenario: Config panel is rendered after actor add
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the output should contain a Config panel
|
|
|
|
Scenario: Config panel shows Path, Hash, Options, Nodes, Edges
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the Config panel should show Path Hash Options Nodes and Edges
|
|
|
|
Scenario: Capabilities panel is rendered when capabilities are present
|
|
Given an actor add CLI runner with capabilities in config
|
|
When I run actor add with the capabilities config
|
|
Then the output should contain a Capabilities panel with the capability list
|
|
|
|
Scenario: Tools panel is rendered when tools are present
|
|
Given an actor add CLI runner with tools in config
|
|
When I run actor add with the tools config
|
|
Then the output should contain a Tools panel with tool rows
|
|
|
|
Scenario: Success status line is printed after all panels
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the output should end with the actor added success line
|
|
|
|
Scenario: No Capabilities panel when capabilities list is empty
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the output should not contain a Capabilities panel
|
|
|
|
Scenario: No Tools panel when tools list is empty
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config
|
|
Then the output should not contain a Tools panel
|
|
|
|
Scenario: Non-rich format skips all extra panels
|
|
Given an actor add CLI runner with a typed config
|
|
When I run actor add with the typed config in json format
|
|
Then the output should be valid JSON without panels
|