56 lines
2.0 KiB
Gherkin
56 lines
2.0 KiB
Gherkin
Feature: CLI Command Coverage
|
|
As a developer
|
|
I want to test all CLI command options and execution paths
|
|
So that coverage includes the command processing logic
|
|
|
|
Background:
|
|
Given the CleverAgents CLI is available
|
|
And I have test configuration files
|
|
|
|
Scenario: CLI run command with basic options
|
|
Given I have a configuration file "test_run.yaml":
|
|
"""
|
|
agents:
|
|
- name: simple_agent
|
|
type: llm
|
|
config:
|
|
model: gpt-3.5-turbo
|
|
"""
|
|
When I run the CLI with config and prompt options
|
|
Then the application should load the configuration
|
|
And the prompt should be processed
|
|
And the output should be generated
|
|
|
|
Scenario: CLI with multiple configuration files
|
|
Given I have multiple configuration files
|
|
When I run the CLI with multiple --config options
|
|
Then all configuration files should be loaded
|
|
And the configurations should be merged properly
|
|
|
|
Scenario: CLI with output file option
|
|
Given I have a valid configuration
|
|
When I run the CLI with --output option
|
|
Then the output should be written to the specified file
|
|
And the file should contain valid response data
|
|
|
|
Scenario: CLI with verbose flag
|
|
Given I have a valid configuration
|
|
When I run the CLI with --verbose flag
|
|
Then detailed logging should be enabled
|
|
And stream processing details should be shown
|
|
|
|
Scenario: CLI with unsafe flag
|
|
Given I have a configuration with unsafe operations
|
|
When I run the CLI with --unsafe flag
|
|
Then unsafe operations should be allowed
|
|
And warning messages should be displayed
|
|
|
|
Scenario: CLI error handling for missing config
|
|
When I run the CLI without any configuration
|
|
Then an appropriate error should be displayed
|
|
And the exit code should indicate failure
|
|
|
|
Scenario: CLI error handling for invalid config path
|
|
When I run the CLI with non-existent config file
|
|
Then a file not found error should be displayed
|
|
And the application should exit gracefully |