Files
cleveragents-core/features/showcase_repl_actor_run.feature
HAL9000 61bdc4bd27
CI / lint (pull_request) Successful in 1m4s
CI / helm (pull_request) Successful in 44s
CI / build (pull_request) Successful in 48s
CI / security (pull_request) Successful in 1m20s
CI / quality (pull_request) Successful in 1m31s
CI / typecheck (pull_request) Successful in 2m7s
CI / push-validation (pull_request) Successful in 25s
CI / unit_tests (pull_request) Successful in 5m45s
CI / docker (pull_request) Successful in 1m36s
CI / integration_tests (pull_request) Successful in 17m3s
CI / coverage (pull_request) Successful in 22m56s
CI / status-check (pull_request) Successful in 3s
fix(showcase): resolve AmbiguousStep for 'the JSON should be valid'
Rename the step decorator in showcase_repl_actor_run_steps.py from
'the JSON should be valid' to 'the examples JSON content is valid'
to avoid collision with the identical step already defined in
aimodelsproviders_steps.py (which uses a different context variable).
Update the matching step text in showcase_repl_actor_run.feature.

ISSUES CLOSED: #7552
2026-06-06 04:58:21 -04:00

81 lines
3.3 KiB
Gherkin

Feature: REPL and Actor Run CLI Showcase Documentation
The showcase documentation for REPL and actor run CLI commands
should be properly registered and accessible.
Scenario: Showcase markdown file exists
Given the showcase directory exists
When I check for the REPL and actor run showcase file
Then the file should exist at "docs/showcase/cli-tools/repl-and-actor-run.md"
Scenario: Showcase is registered in examples.json
Given the examples.json file exists
When I check for the REPL and actor run showcase entry
Then the entry should have title "REPL and Actor Run: Interactive AI Sessions from the Terminal"
And the entry should have category "cli-tools"
And the entry should have path "cli-tools/repl-and-actor-run.md"
And the entry should have complexity "intermediate"
Scenario: Showcase has required commands documented
Given the showcase markdown file exists
When I check the documented commands
Then the file should contain "agents repl"
And the file should contain "agents actor run"
And the file should contain "agents repl --help"
And the file should contain "agents actor run --help"
Scenario: Showcase has REPL section
Given the showcase markdown file exists
When I check the content structure
Then the file should contain "Part 1: The Interactive REPL"
And the file should contain ":help"
And the file should contain ":exit"
And the file should contain "!!"
Scenario: Showcase has Actor Run section
Given the showcase markdown file exists
When I check the content structure
Then the file should contain "Part 2: Single-Shot Actor Run"
And the file should contain "--config"
And the file should contain "--output"
And the file should contain "--temperature"
And the file should contain "--context"
Scenario: Showcase has real output examples
Given the showcase markdown file exists
When I check for verified output
Then the file should contain "Actual Output:"
And the file should contain "verified"
Scenario: Examples.json has valid JSON structure
Given the examples.json file exists
When I parse the JSON
Then the examples JSON content is valid
And the JSON should have "examples" key
And the JSON should have "categories" key
Scenario: Showcase entry has all required fields
Given the examples.json file exists
When I check the REPL and actor run entry
Then the entry should have "title" field
And the entry should have "category" field
And the entry should have "path" field
And the entry should have "feature" field
And the entry should have "commands" field
And the entry should have "complexity" field
And the entry should have "educational_value" field
Scenario: Showcase commands list is not empty
Given the examples.json file exists
When I check the REPL and actor run entry
Then the commands list should have at least 5 items
And the commands should include "agents repl"
And the commands should include "agents actor run"
Scenario: Showcase file has proper markdown formatting
Given the showcase markdown file exists
When I check the markdown structure
Then the file should start with a heading
And the file should have multiple sections
And the file should have code blocks
And the file should have proper link formatting